-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add support for PEP 440 version specifiers in the --python flag.
#3008
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 support for PEP 440 version specifiers in the --python flag.
#3008
Conversation
|
Test succeeding(one timeout): https://github.com/rahuldevikar/virtualenv/actions/runs/20672977256 New run(increased timeout): https://github.com/rahuldevikar/virtualenv/actions/runs/20673442400 |
4437b46 to
4afaf6c
Compare
gaborbernat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI is also failing.
…/rahuldevikar/virtualenv into users/rahuldevikar/fix2994_clean
Add PEP 440 version specifier support for --python flag
Implements support for using PEP 440 version specifiers with the --python flag,
allowing users to specify Python versions using operators like >=, <=, ~=, etc.
Examples:
Changes:
Fixes #2994
Use any Python >= 3.12
virtualenv --python=">=3.12" myenv
Use CPython ~= 3.11.0 (compatible release)
virtualenv --python="cpython~=3.11.0" myenv
Use Python between 3.10 and 3.13
virtualenv --python=">=3.10,<=3.13" myenv
With implementation prefix
virtualenv --python="python>=3.11" myenv