Switch to pixi

[stanmart]

Checklist

• Added a CHANGELOG.rst entry

Similarly to glum #802, this migrates the dev installation to pixi. It's more or less the same, so see that PR for the discussion.

TODO:

• Fix the typing issues that mypy finds now that it sees the dependencies.
• Find minimal versions of the required packages (and update oldies environment accordingly_)
• Make readthedocs work
• Fix benchmark-analyze (although I don't think it is a pixi issue)
• Update contributing instructions

[stanmart]

Since submitting this PR the a new version of pixi has been released, which supports passing the no-build-isolation flag to uv. Maybe it's time to get rid of the postinstall workaround? I gave it a quick test and works, but there are a couple of caveats:

• It makes package resolution somewhat slower (I think it makes sure that the dependencies for tabmat are installed).
• I have not yet figured out how to manually trigger a rebuild of the package, which is necessary when the C++/Cython modules are changed.

What do you think @pavelzw?

[MarcAntoineSchmidtQC]

I left 2 questions regarding the CI setup, but otherwise looks good. Tested on my mac and everything works perfectly.

[MarcAntoineSchmidtQC]

Regarding the switch to the no-build-isolation using pixi, how slow does it make the package resolution? Is it going from like 10 seconds to 2 minutes, or from 10 seconds to 15 seconds? If it's the latter, then I'm absolutely okay with that.

For the rebuild, either we can keep the post-install task or rename it to "rebuild". Also, as this is only relevant for deep development, we can also instruct the contributors to remove the lock file and start from scratch.

[stanmart]

Is it going from like 10 seconds to 2 minutes, or from 10 seconds to 15 seconds?

If we make this change then pixi has to install an environments before being able to make the final solve. I did some testing: this means that from starting from scratch, environment resolution (e.g. when adding a new package) takes ~2 minutes on my laptop. Another issue is that these environments take up a lot of space (11 gigs). After all environments are installed, resolution is reasonably fast (e.g. adding a package takes around 10-15 seconds.

I'd say making devs install all environments when they want to add a dependency is too big of a tradeoff (especially in terms of disk space) for being able to omit postinstall. I would wait until pixi gets a no-dependencies flag for pypi dependencies, or some other solution.

For the rebuild, either we can keep the post-install task or rename it to "rebuild". Also, as this is only relevant for deep development, we can also instruct the contributors to remove the lock file and start from scratch.

Good point! Even though I would not make the switch just yet, it would be a perfect solution when we do.

[pavelzw]

Another issue is that these environments take up a lot of space (11 gigs)

xref prefix-dev/pixi#1046