Cannot pip install by default any more

Bug #2032801 reported by Robie Basak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
New
Undecided
Unassigned

Bug Description

Since Lunar or maybe Kinetic, "pip install" won't work on the system and requires a virtualenv unless you use --break-system-packages. But I don't see this release noted in the past.

People will notice and see it as a breaking change, so we should release note it. For example, Dockerfiles that use "pip install" will break and users will either have to use --break-system-packages or arrange virtualenvs, even though within a Docker environment, if it works it's not usually an issue.

We should probably document this and have recommended answer for various use cases.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.