bug: parsing of compatible release clause

PyO3 / maturin-action

GitHub Action to install and run a custom maturin command with built-in support for cross compilation

MIT License

132 stars 37 forks source link

bug: parsing of compatible release clause #286

Open ddelange opened 2 months ago

ddelange commented 2 months ago

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: https://github.com/ddelange/blake3-py/pull/1/commits/2d56b535f32ae61bffb80d974db8bb039bebf56e

Found during development: https://github.com/oconnor663/blake3-py/pull/45

messense commented 1 month ago

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

ddelange commented 1 month ago

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