Use uv / pixi? - Githubissues

zarr-developers / VirtualiZarr

Create virtual Zarr stores from archival data files using xarray syntax

https://virtualizarr.readthedocs.io/en/stable/api.html

Apache License 2.0

123 stars 24 forks source link

Use uv / pixi? #310

Open TomNicholas opened 2 days ago

TomNicholas commented 2 days ago

without much context, obligatory pixi endorsement comment

emerging from a rabbit hole (thanks @cisaacstern 😂) I'm floating around this decision framework for feedback:

If you're starting a new Python package, use uv
If you need to manage multiple Python virtual environments at a time, also use hatch
If you need Conda-Forge in addition to PyPI distributions, ~~also~~ use pixi

More on topic, feel welcome to ping me if you'd like to assign any CI / packaging updates.

Originally posted by @maxrjones in https://github.com/zarr-developers/VirtualiZarr/issues/309#issuecomment-2486738368

cisaacstern commented 2 days ago

In general I think this decision framework makes sense, though (with the caveat that I've never used hatch environments) I might omit the middle bullet to make it just

If you're starting a new Python package [and don't conda dependencies], use uv
If you need Conda-Forge in addition to PyPI distributions, use pixi

Pixi will manage multiple environments for use in ci, and switching to pixi would mean being able to entirely remove the ci/ directory from this project, moving all of what's specified there into the pixi.toml manifest file, or put directly into the [tool.pixi] table of the pyproject.toml if you prefer.

cisaacstern commented 2 days ago

Pixi will manage multiple environments for use in ci, and switching to pixi would mean being able to entirely remove the ci/ directory from this project, moving all of what's specified there into the pixi.toml manifest file, or put directly into the [tool.pixi] table of the pyproject.toml if you prefer.

I've been meaning to help out with this project somehow, and if this is of interest, I could make a PR to demonstrate.

maxrjones commented 2 days ago

Pixi will manage multiple environments for use in ci, and switching to pixi would mean being able to entirely remove the ci/ directory from this project, moving all of what's specified there into the pixi.toml manifest file, or put directly into the [tool.pixi] table of the pyproject.toml if you prefer.

I've been meaning to help out with this project somehow, and if this is of interest, I could make a PR to demonstrate.

I expect that we'll want conda for some of the drivers, so pixi seems like a good option to me for virtualizarr. plus I'd be excited to learn from your PR 😄

TomNicholas commented 2 days ago

if this is of interest, I could make a PR to demonstrate.

This is definitely of interest, and I would love it if you could point us to how it should be done 😁

cisaacstern commented 2 days ago

Great to know! I'd love to share a PR showing how I'd approach it and get all of your feedback.

Are any other outstanding issues / PRs dependent on this, or are there any deadlines this is needed for?

I will try to get to it ASAP but want to make sure I don't accidentally miss some important context.

TomNicholas commented 2 days ago

Are any other outstanding issues / PRs dependent on this, or are there any deadlines this is needed for?

No none at all. It's already distributed through pip and conda, this would just be modernizing / a quality of life improvement.