Add pixi

[wolfv]

Checklist

• Used a static YAML file for the patch if possible (instructions).
• Only wrote code directly into generate_patch_json.py if absolutely necessary.
• Ran pre-commit run -a and ensured all files pass the linting checks.
• Ran python show_diff.py and posted the output as part of the PR.
• Modifications won't affect packages built in the future.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[hmaarrfk]

is a pixi lock file for a "small project" such as this really 5k lines long?

[wolfv]

It will become a little shorter soon (we remove some duplicate data in a upcoming PR). But yeah, since we need the repodata records it is rather long.

[bollwyvl]

I think the approach from staged-recipes of not checking in the pixi.lock is going to be the right play here. On account of that, the bottom dependency versions should be tightened a fair amount and kept in sync with the meta.yaml so that migrations trickle down into pixi.toml and trigger a re-lock locally as needed.

I could definitely see a useful pixi r pr top-level command that:

• pixi r lint
  • validated all patches
• pixi r diff
  • ran show_diff.py
    • wrote it out to $(git rev-parse --abbrev-ref HEAD).diff.md for easy of copy-pasting and review

[jdblischak]

Could you please also add some documentation to recipe/README.md to alert contributors that the pixi configuration exists and how they can use it to test their patches? I'm imagining something similar to #675 where I added a conda env file

[bollwyvl]

Already a dependency of pydantic...

[bollwyvl]

I... don't believe this can be *... I'd wager 2.* might be safe, but there are a lot of pins out there...

[bollwyvl]

as this is:

• very expensive, I recommend adding a description noting that
• _very_verbose, probably also a task which writes it out to a > {git branch}.txt

[bollwyvl]

pre-commit isn't going to fire unless inside a shell... having a task.lint that runs all the linters against all the files would likely be helpful.

[bollwyvl]

I'm not convinced checking in the pixi.lock is a net win for this particular project...