This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients FFY00, frenzy, hroncok, jaraco, lemburg, petr.viktorin, steve.dower
Date 2021-05-04.20:23:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <6e7e06bb-2fc1-c959-e6ee-8d7ddbb371e1@egenix.com>
In-reply-to <1620158857.89.0.579462586802.issue43976@roundup.psfhosted.org>
Content
On 04.05.2021 22:07, Steve Dower wrote:
> 
> Perhaps what I'm suggesting here is that I don't see any reason for "sudo pip install ..." into a distro-installed Python to ever need to work, and would be quite happy for it to just fail miserably every time (which is already the case for the Windows Store distro of Python).

The "pip install" into a root environment approach is the standard way
to setup Docker (and similar) containers, so I think trying to break
this on purpose will not do Python a good service.

The pip warning about this kind of setup which apparently got added
in one of the more recent versions of pip already is causing a lot
of unnecessary noise when building containers and doesn't make Python
look good in that environment.
History
Date User Action Args
2021-05-04 20:23:08lemburgsetrecipients: + lemburg, jaraco, petr.viktorin, steve.dower, hroncok, frenzy, FFY00
2021-05-04 20:23:08lemburglinkissue43976 messages
2021-05-04 20:23:08lemburgcreate