pixi icon indicating copy to clipboard operation
pixi copied to clipboard

Add pixi version to system requirements

Open pablovela5620 opened this issue 1 year ago • 4 comments

Problem description

Often times I'll have a project that I made some time ago, which I think is still reproducible with its lock file, but fails because I'm using a different version of pixi. A potential solution may be to add an optional pixi version to the system-requirements table. This would help ensure folks don't run into situations where they think things will work further down the line, but because of a regression they dont

pablovela5620 avatar Aug 30 '24 17:08 pablovela5620

Do you mean like a pinned version, or a minimum required version? :)

tdejager avatar Aug 30 '24 17:08 tdejager

I think a pinned version, but maybe both? not sure the best way to handle it. I can give a concrete example

Nerfstudio has the following pixi.toml https://github.com/nerfstudio-project/nerfstudio/blob/main/pixi.toml

using 0.28.2 this fails for me and I get

pixi install
  ⠠ default:linux-64     [00:00:01] resolving tomli==2.0.1                                                                                                                                                          × failed to solve the pypi requirements of 'default' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ├─▶ Failed to download and build `fire==0.6.0`
  ├─▶ Failed to install requirements from build-system.requires (install)
  ├─▶ Failed to prepare distributions
  ├─▶ Failed to fetch wheel: setuptools==69.5.1
  ├─▶ Failed to extract archive
  ╰─▶ Invalid gzip header

but with 0.25.0 it resolves no problem

pablovela5620 avatar Aug 30 '24 18:08 pablovela5620

I like this idea!

Note that the system requirements are mostly lower bound only.

[system-requirements]
pixi = "<=0.25.0"
cuda = "<=12.1" # Errors

But that might not be a huge problem. As it is non standard anyway.

ruben-arts avatar Aug 30 '24 21:08 ruben-arts

Yes, this exactly would be perfect!

pablovela5620 avatar Aug 31 '24 00:08 pablovela5620

Now that pixi.toml recently broke forward compatibility, this would be particularly useful - we have users coming in with latest pixi and then not being able to use it because we're still on pixi 0.39 but 0.40 can't handle the file anymore. See

  • https://github.com/rerun-io/rerun/issues/8665

Wumpf avatar Jan 13 '25 14:01 Wumpf

You can now use requires-pixi:

[workspace]
requires-pixi = "0.55.0"

ruben-arts avatar Oct 02 '25 09:10 ruben-arts