-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
virtualenv silently ignores requested pip version if not available #2485
Comments
PR welcome. |
Can I work on this one? I am pretty new to this |
Found this issue and after trying to reproduce the problem I seem to retrieve the expected pip version on my machine (using Ubuntu 22.04 on WSL and virtualenv 20.23.0). Note that I also used Using the same command (added --with-traceback) and Python/pip versions:
I also upgraded my global pip to 23.1.2 to see if that somehow has changed anything but got the same results. I don't have knowledge of how virtualenv works, but my educated guess is your printout looks weird as when you used On virtualenv 20.23.0, this seems to be no longer an issue (at least on my machine). |
PR welcome. |
I apologize as I must have not worded my comment in a better way. I ran the version of virtualenv that the author used (20.0.17) and using the same command and Python/pip version given I was able to reproduce this problem. But when I ran using virtualenv 20.23.0, I was given the expected pip version when running |
When I try to
When I try to reproduce the error in @gaborbernat I think with the new version of |
Issue
I'm trying to pin the version of
pip
my virtual envs will have, regardless of the version of virtualenv being used. I realized that if the requested pip version is not available then virtualenv just picks the latets, silently.Check the following example where I request an older pip version,
20.0.1
, but I end up with22.3.1
. On the other hand, if I request20.0.2
it works as expected.Environment
Provide at least:
pip list
of the host python wherevirtualenv
is installed:Output of the virtual environment creation
Make sure to run the creation with
-vvv --with-traceback
:The text was updated successfully, but these errors were encountered: