Package: python3.10 Version: 3.10.2-5 Severity: important As of python3.10 3.10.2-3, python3.10 -m venv installs pip to the wrong path:
# apt update # apt install python3.10-venv # python3.10 -m venv /tmp/my-venv # . /tmp/my-venv/bin/activate # type pip bash: type: pip: not found # pip --version bash: pip: command not found # echo $PATH /tmp/my-venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin # ls /tmp/my-venv/bin Activate.ps1 activate activate.csh activate.fish python python3 python3.10 # ls /tmp/my-venv/local/bin pip pip3 pip3.10 There’s a similar problem with virtualenv; although virtualenv still installs pip to the correct path, that pip installs other binaries to the wrong path: # deactivate # apt install python3-virtualenv # virtualenv -p python3.10 /tmp/my-virtualenv # /tmp/my-virtualenv/bin/pip install black # . /tmp/my-virtualenv/bin/activate # type black bash: type: black: not found # black --version bash: black: command not found # ls /tmp/my-virtualenv/local/bin black black-primer blackd This all worked correctly in 3.10.2-2. # deactivate # echo deb https://snapshot.debian.org/archive/debian/20220224T145813Z/ sid main >> /etc/apt/sources.list # apt update # apt install {libpython3.10-minimal,libpython3.10-stdlib,python3.10,python3.10-minimal,python3.10-venv}=3.10.2-2 # rm -rf /tmp/my-venv /tmp/my-virtualenv # python3.10 -m venv /tmp/my-venv # . /tmp/my-venv/bin/activate # type pip pip is /tmp/my-venv/bin/pip # pip --version pip 22.0.2 from /tmp/my-venv/lib/python3.10/site-packages/pip (python 3.10) # deactivate # virtualenv -p python3.10 /tmp/my-virtualenv # /tmp/my-virtualenv/bin/pip install black # . /tmp/my-virtualenv/bin/activate # type black black is /tmp/my-virtualenv/bin/black # black --version black, 22.1.0 (compiled: yes)
