On 2023-03-03 16:22:11 -0500 (-0500), Jorge Moraleda wrote: > I did not know about `sudo pip install --break-system-packages > foo` or `sudo rm /usr/lib/python3.11/EXTERNALLY-MANAGED` (Frankly > I only knew about this issue what I have read on this discussion). [...] They come from a reading of the pip documentation and associated PEP-668 specification respectively. I do hope power users read documentation before they choose to break their systems. Be aware that the second approach I mentioned is removing a file which gets installed by the libpython3.11-stdlib package, so will end up getting replaced each time you upgrade that package as it's not a conffile. It's a reasonable approach for things like container base images where subsequent image build steps use pip to install packages into the container, but it would be annoying for a "normal" system where you upgrade packages without building entirely new images. The pip install command-line option is more of a user-facing escape hatch, since it's clearly worded to let you know that it can quite easily render existing Python applications inoperable if you choose to install things into user or system site directories with pip. -- Jeremy Stanley
Attachment:
signature.asc
Description: PGP signature