Skip to content
New issue

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

Python 2.0 selected when installing with zlib #1292

Open
2 tasks done
benmoss opened this issue Apr 27, 2024 · 1 comment
Open
2 tasks done

Python 2.0 selected when installing with zlib #1292

benmoss opened this issue Apr 27, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@benmoss
Copy link

benmoss commented Apr 27, 2024

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

pixi init --platform linux-64 --platform osx-arm64
pixi add python zlib

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

@benmoss benmoss added the bug Something isn't working label Apr 27, 2024
@ruben-arts
Copy link
Contributor

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.

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants