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

Support for compatible release operator ~= #29

Open
y0m1g opened this issue Apr 30, 2020 · 0 comments
Open

Support for compatible release operator ~= #29

y0m1g opened this issue Apr 30, 2020 · 0 comments
Assignees
Labels

Comments

@y0m1g
Copy link

y0m1g commented Apr 30, 2020

Hello,

I've noticed pur does not support the compatible release operator, i.e. ~=.
As described PEP-0440, ~= 1.4.5 is equivalent to >= 1.4.5, == 1.4.* (https://www.python.org/dev/peps/pep-0440/#compatible-release), but even if pur is able to update from click >= 7.1.0, == 7.1.* to click >= 7.1.2, == 7.1.*, it does nothing with click ~= 7.1.0.
I suppose this would be the appropriate behaviour to implement in pur.

That being said, it wouldn't fit my personal use case: basically I'm usually "soft-pinning" my requirements, meaning specifying boto3 ~= 1.12.49 instead of using the == operator, to allow security patches and also avoid dependency hell when I'm using inter-dependent modules.
So in my case, using requirements with ~= operator, I would prefer pur to behave just like it does with the == operator, meaning updating to the latest available version.
Would there be a way to enable this behaviour somehow while staying PEP-0440 compliant?

Thanks.

@alanhamlett alanhamlett self-assigned this Jul 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants