This bug is about a Debian-user-specific issue (not wanting to depend on PyPI), but I don't think this is something Debian should try to solve, alone. Mentions a -break-system-packages (as an example), but such an option To tell it to allow me to install to ~/.local anyway. Have all dependencies provided by Debian packages, not downloaded fromĪnd as far as I can tell there is not even an option I can give to pip User account with 'pip install -e', which is also made impossible byĪnd I intentionally do not use virtualenvs for this because I want to Not being able to install packages system-wide seems like a good idea,īut I often install the Python packages I'm developing under my own

See /usr/share/doc/python3.11/README.venv for more details. Virtualenv, on a Debian system, any more. Practically, this means that you can't use pip to install packages outside a Interpreter will soon (>= 3.11.1-3) declare the installation to beĮXTERNALLY-MANAGED, instructing pip to disallow package installation outside This version of pip introduces PEP 668 support. I just updated python3-pip and was greeted with a NEWS message about I think it's best if this is discussed here, with upstream involvement.Ĭc who were involved in the PEP or pip in Debian. Filed Debian bug #1030335 about the implementation of PEP 668 support.

Debian install pip3