-
Notifications
You must be signed in to change notification settings - Fork 209
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
Add version range to pypi-dependencies when using pixi add --pypi
#1409
Comments
It would make sense to be consistent between pypi and conda packages. Maybe not a bug but a enhancement? |
pixi add --pypi
I just want to emphasize that this "enhancment" is critical for adoption of pixi since it is needed to achieve reproducible package builds. Hope someone finds the time to tackle this one, I would but I am not experienced in Rust. |
@ruben-arts I though this was already implemented with the latest release? |
I thought so too but want to make sure before closing the issue. |
This is was actually fixed already in #1508. Closing this as fixed. @SeanPedersen Are you trying with the latest release? If so and it still doesn't work, can you open a new issue with the non working |
Everything works as expected with the latest release, thanks a lot. |
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
Issue description
Maybe I just have the wrong expectations, but when I added a package via the
--pypi
flag, the package was simply added like this topyproject.toml
:dependencies = ["edudata"]
Is this the expected behaviour or should the package be added with default version ranges as discussed in #639?
Thank you
Expected behavior
Expected dependencies:
dependencies = ["edudata >=0.0.18,<0.1"]
The text was updated successfully, but these errors were encountered: