Closed vfrico closed 2 years ago
this is an unfortunate packaging decision on the part of debian, I would suggest using virtialenv
from pypi instead (which won't have the devendoring blunder)
they've fixed this for the next lts but nothing can really be done for 20.04
I'm getting this same behavior using python3.10 -m pip
outside a virtualenv too. @asottile Is that for the same reason?
I was about to do a python3.10 -m pip install --user virtualenv
to follow your previous advice. How would you go about that?
I also got that behaviour from preinstalled pip, maybe it’s because of the old version (20.0.2 vs 21.3.1)?
Unfortunately get-pip.py
doesn’t work when used for the global install — for some reason it just breaks pip (I get no module named “pip”
afterwards, assuming you set Python 3.10 as default using update-alternatives
, otherwise it installs pip for the default python even if you invoke with python3.10
). I seem to have got around this by just user-installing pip: python3.10 get-pip.py --user
.
yeah that's tracked in #182 -- basically cpython changed the sysconfig initialization again and I haven't copied the relevant patch yet from debian
yeah that's tracked in #182 -- basically cpython changed the sysconfig initialization again and I haven't copied the relevant patch yet from debian
Oh, okay. Thanks.
I seem to have got around this by just user-installing pip:
python3.10 get-pip.py --user
.
I'll use this then meanwhile. Thanks.
For the benefit (maybe) of other Debian / Ubuntu users who find this issue after a web search: Another workaround is to create the virtualenv with python3.10 -m venv $ENV_NAME
. For me, this solved it.
Description
I've created a virtualenv using the 3.10 interpreter, but pip does not work inside it.
os information
I have installed all the packages available for Ubuntu 20.04 in the PPA repository
lsb_release -a
uname -a