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

bug: parsing of compatible release clause #286

Open
ddelange opened this issue Sep 23, 2024 · 2 comments
Open

bug: parsing of compatible release clause #286

ddelange opened this issue Sep 23, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@ddelange
Copy link

Setting maturin~=1.0 (compatible release clause equivalent to maturin>=1.0,<2) in pyproject.toml will result in maturin-action picking v1.0.1 instead of v1.7.1.

Quick fix for users: ddelange/blake3-py@2d56b53

Found during development: oconnor663/blake3-py#45

@ddelange ddelange changed the title Fix parsing of compatible release clause bug: parsing of compatible release clause Sep 24, 2024
@messense
Copy link
Member

This is actually a known issue because the version spec in Python isn't standard semver.

@messense messense added the bug Something isn't working label Sep 25, 2024
@ddelange
Copy link
Author

ddelange commented Sep 25, 2024

yeah, tell me about it... many small struggles in pipgrip 😄

easiest way to go from ~=1.0 to 1.7.2 is to parse the json output from this command:

pip install -q --dry-run --report - --no-deps --ignore-installed -- maturin~=1.0

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