misc: use pixi for the source build #16
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just a test!
If you were interested, this would be fun to merge.
What does it do?
This setup now uses
pixi buildto build the python source into a conda package, instead of a recipe file.Running
pixi buildwill actually make a standalone conda package.Running
pixi installwill install the package directly into your environment.This is similar to
pypi-dependenciespathstyle. But instead ofuvit uses rattler-build to build the package into a installable package. This also works with editable (this is the default).Changes
pixi.tomlto make the file more readable (not needed but I liked it while working on it)[package]table to define the conda metadata in the pixi.tomlbuildenvironment as that doesn't do much.TODO
This isn't translated to CI yet. Would first like to know if you would have interest in this.