4 ms·

Python developers agree. See PEP 668 – Marking Python base environments as “externally managed” – https://peps.python.org/pep-0668/ https://peps.python.org/pep-

• brylie 2y ago
  More recent document https://packaging.python.org/en/latest/specifications/externally-managed-environments/#externally-managed-environments https://packaging.python.org/en/latest/specifications/extern...
  • ajb 2y ago
    Hmm that still recommends that distros allow admins to install to /usr/local, albeit in such a way that it at least can't break the OS. IMO the idea that a 'Linux admin' is better informed than a 'Linux user' is increasingly anachronistic. In most cases the admin is just the user running sudo. I'd suggest that such functionality should be enabled by installing some kind of OS package rather than being the default
• jampekka 2y ago
  Yet another hack on hack. Venv was the wrong fix/hack and now the package management is cascading into even more madness.
• lhfacx 2y ago
  This is insane. Apparently (at least on Debian) this can be circumvented by putting this in ~/.config/pip/pip.conf: [global] break-system-packages = true I would have preferred single-version-externally-managed to keep fond memories of setuptools alive. It becomes increasingly impossible to track down home directory pollution and config files in Python. Next step will be a Python registry on Linux. How about: regedit VENV=/home/sjw/venv42 KEYWORD=single-version-externally-managed DWORD=0xbadbee