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

New Virtualenv installing beta pip3 (10.0.0b2) #1157

Closed
jwarren116 opened this issue Apr 3, 2018 · 5 comments
Closed

New Virtualenv installing beta pip3 (10.0.0b2) #1157

jwarren116 opened this issue Apr 3, 2018 · 5 comments

Comments

@jwarren116
Copy link

I'm running Python 3.5.2 (/usr/bin/python3.5), with Pip3 8.1.1 (/usr/bin/pip3) on Ubuntu 16.04 with python3-virtualenv installed via apt. Under dpkg, the version is python3-virtualenv/xenial-updates 15.0.1+ds-3ubuntu1 all.

When I create a new environment by running the following command:

virtualenv --python=/usr/bin/python3.5 env

I am expecting the pip3 version to be 8.1.1 (the only pip3 that's installed on my system). Instead I activate the virtual env and pip --version outputs the following:

pip 10.0.0b2 from /home/ubuntu/env/lib/python3.5/site-packages/pip (python 3.5)

As an interim solution I am able to downgrade immediately after creating the environment, however this seems like it shouldn't be the intended behavior. Please let me know if or what additional information would be helpful.

@pfmoore
Copy link
Member

pfmoore commented Apr 3, 2018

Do you have a PIP_PRE environment variable, or a pip configuration file that specifies the --pre argument? Or has your distribution patched pip to install prerelease versions (unlikely, I'd have thought). Can you reproduce this behaviour with the virtualenv from PyPI (or github)?

@jwarren116
Copy link
Author

Sorry, I meant to include that as well! I have no PIP* vars set in the environment, and there's no pip config file. I don't believe the dist has been patched, but I haven't been able to verify.

I will try to reproduce with virtualenv from PyPI or Github and circle back.

@jmbowman
Copy link

jmbowman commented Apr 3, 2018

@jwarren116 I believe virtualenv fetches the latest available versions of setuptools, pip, and wheel from PyPI when it creates a new virtualenv (using a local pip cache if available). And until virtualenv 15.1.0, it internally set "PIP_PRE=1" when doing that. So upgrading to virtualenv 15.1.0 or above will at least get you pip 9.0.3 installed in new virtualenvs instead. If you specifically want pip 8.1.1 in your virtualenv, I think you'll need to explicitly downgrade it after creation.

@pfmoore
Copy link
Member

pfmoore commented Apr 4, 2018

@jmbowman Thanks for that clarification. I knew I recalled that virtualenv set PIP_PRE, but couldn't find it in a dive through the sources. It didn't occur to me to go back in history.

@stale
Copy link

stale bot commented Jan 14, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 14, 2019
@stale stale bot closed this as completed Jan 21, 2019
@pypa pypa locked and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants