-
-
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
20.0.19 does not install pip on Python 3.4 #1809
Labels
Comments
Hello, this now has been released via https://pypi.org/project/virtualenv/20.0.20/ |
Wow. Super fast! Thanks!! |
I verified that it works again with virtualenv 20.0.20. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue
In Travis with Python 3.4, virtualenv 20.0.19 does not seem to install a pip into a newly created virtualenv when creating it while a virtualenv is already acrive. "which pip" returns the pip from the first virtualenv after the new one is created and active. It fails only on Python 3.4 (the errors with pypy in the Travis logs below have a different cause). virtualenv before 20.0.19 does not have that behavior and succeeds on Python 3.4.
Version and location of Python and Pip after having activated the second virtualenv: Note that Python is shown to come from the correct second virtualenv while Pip is shown to come from the incorrect first virtualenv that Travis had set up:
To see this in the Travis logs, search for "Creating virtualenv:" case sensitively (around line 2500):
Environment
Provide at least:
pip list
of the host python wherevirtualenv
is installed:see Travis logs
Output of the virtual environment creation
Make sure to run the creation with
-vvv --with-traceback
:see Travis logs
The text was updated successfully, but these errors were encountered: