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

How to update pip permanently for new venv? #1852

Closed
tbrodbeck opened this issue Jun 10, 2020 · 4 comments
Closed

How to update pip permanently for new venv? #1852

tbrodbeck opened this issue Jun 10, 2020 · 4 comments

Comments

@tbrodbeck
Copy link

Describe the bug
Every new environment has the old pip version (19.2.3)

Expected behavior
My system python has pip version 20 so I would expect direnv also to use the most recent pip version. But it installs the old pip version for every new environment

Environment

  • OS: macOS Catalina 10.15.4
  • Shell: zsh 5.7.1
  • Python version: stable 3.7.7 (homebrew bottled)

To Reproduce

~ pip list
Package            Version
------------------ -------
appdirs            1.4.4
astroid            2.4.1
distlib            0.3.0
filelock           3.0.12
importlib-metadata 1.6.1
isort              4.3.21
lazy-object-proxy  1.4.3
mccabe             0.6.1
numpy              1.18.5
pip                20.1.1
pylint             2.5.2
python-dateutil    2.8.1
pytz               2020.1
setuptools         40.8.0
six                1.12.0
toml               0.10.1
typed-ast          1.4.1
virtualenv         20.0.21
wheel              0.33.1
wrapt              1.12.1
zipp               3.1.0~ python3 -m venv ./foobar~ source ./foobar/bin/activate
(foobar) ➜  ~ pip list
Package    Version
---------- -------
pip        19.2.3 
setuptools 41.2.0 
WARNING: You are using pip version 19.2.3, however version 20.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
@pradyunsg
Copy link
Member

#1841 will address this need.

@gaborbernat
Copy link
Contributor

I'd just like to mention that you're using venv module, not virtualenv. Feature requests for those should be filled under https://bugs.python.org/, not here. Note venv is not virtualenv - see https://virtualenv.pypa.io/en/latest/. That being said if you're fine with paying the performance penalty passing in the --download should help.

@tbrodbeck
Copy link
Author

Ok interesting. I opened an issue on https://bugs.python.org/issue40940 then.

@pradyunsg pradyunsg removed the bug label Jun 10, 2020
@pradyunsg
Copy link
Member

I'd just like to mention that you're using venv module, not virtualenv

oooo. I missed that. :)

@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