We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using pixi --version.
pixi --version
On an osx-arm64 machine with pixi 0.20.1
pixi init --platform linux-64 --platform osx-arm64 pixi add python zlib
It picks Python 2.0 for linux-64 and Python 3.12.3 for osx-arm64
I think it should pick 3.12.3 for both
The text was updated successfully, but these errors were encountered:
That is an interesting find! Our solver tries to use the highest versions but this time it got exactly what you don't want.
python 3.x.x has a dependency of libzlib of <=1.2.13,<1.3.0a0 but for some reason the solver chose to pick libz 1.3.1 before the python version.
python 3.x.x
<=1.2.13,<1.3.0a0
libz 1.3.1
python
@baszalmstra Do you know if this is a issue in pixi or this is is part of resolvo. And you we could avoid this?
A quick fix would be to limit zlib or python yourself. E.g. pixi add "python>3.7" zlib
pixi add "python>3.7" zlib
Sorry, something went wrong.
No branches or pull requests
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
On an osx-arm64 machine with pixi 0.20.1
Issue description
It picks Python 2.0 for linux-64 and Python 3.12.3 for osx-arm64
Expected behavior
I think it should pick 3.12.3 for both
The text was updated successfully, but these errors were encountered: