Package: python3-pip
Version: 23.0+dfsg-1
Severity: important
X-Debbugs-Cc: [email protected]

Hi!

I just updated python3-pip and was greeted with a NEWS message about
PEP 668 support:

  This version of pip introduces PEP 668 support. Debian's python3.11
  interpreter will soon (>= 3.11.1-3) declare the installation to be
  EXTERNALLY-MANAGED, instructing pip to disallow package installation outside
  virtualenvs.
  
  See: https://peps.python.org/pep-0668/
  
  Practically, this means that you can't use pip to install packages outside a
  virtualenv, on a Debian system, any more.
  
  See /usr/share/doc/python3.11/README.venv for more details.
  If that isn't available yet, check:
  https://salsa.debian.org/cpython-team/python3/-/blob/master/debian/README.venv

Not being able to install packages system-wide seems like a good idea,
I fully support that.

But I often install the Python packages I'm developing under my own
user account with "pip install -e", which is also made impossible by
this change.

And I intentionally do not use virtualenvs for this because I want to
have all dependencies provided by Debian packages, not downloaded from
PyPI.

And as far as I can tell there is not even an option I can give to pip
to tell it to allow me to install to ~/.local anyway.  PEP 668
mentions a --break-system-packages (as an example), but such an option
doesn't seem to actually exist.

- FC

Reply via email to