So what are the alternatives to using pip install directly? Take a look below:ġ. I said "likely adopt" because, even though this change is already present in Debian Testing and Ubuntu 23.04 Lunar Lobster, Stefano Rivera, one of the Debian/Ubuntu Python maintainers, mentioned that " if necessary, we can roll back EXTERNALLY-MANAGED in our python3.11 for bookworm’s release, but I’d like to make this happen…". There's also a proposal to include this in Fedora 38 (which had a beta release today), but this has not landed in Fedora 38 for now. The change is already live in Debian Testing and Ubuntu 23.04 Lunar Lobster (which will have a beta release on March 30, with the final release expected on April 20). This can still be forced though, and obviously, there are alternatives.
The breakage can occur for both system-wide pip installations ( sudo pip install), as well as user installations ( pip install -user), but especially the latter, since trying to recover from this might result in removing (using pip, not the distro package manager) packages installed using the Linux distribution's package manager.įor this reason, the next Debian (Debian 12 Bookworm) and Ubuntu (Ubuntu 23.04 Lunar Lobster) releases will likely adopt PEP668 (PEP = Python Enhancement Proposal), marking the Python base environments as "externally managed", and no longer allowing regular pip install usage for both user and system installations. And this isn't even about breaking some application-because Python is so widely used nowadays, users can easily break critical distro packages. All the user has to do is install a package (or some of its dependencies) that's newer and backwards-incompatible with a version that was installed from the Linux distribution official repositories.
Software shipped with a Linux distribution can be (quite easily, I might add) broken by installing packages using pip. It can still be forced, but that's strongly not recommended. The next Debian/Ubuntu releases will likely no longer allow pip install outside a virtual environment or separate Python installs because of conflicts between pip and the OS package manager.
0 kommentar(er)
