I'm not a member of the SIG, but as someone who did this in the past
before learning proper practices, I would find this *extremely* helpful,
especially when running certain software that explicitly tells the user
to run this, even with it being bad practice.
A big +1 from me…
On 02/10/2017
Having been badly burned by sudo pip install in the past, I agree that a
warning is appropriate, with a suggestion to use pip install --user
On Fri, Feb 10, 2017 at 1:28 PM Tomas Orsava wrote:
> Hi!
> On the last FESCo meeting while discussing the sudo pip Fedora [Change],
>
Since it is fixed upstream I'll backport the fix for rawhide and the stable
Fedora's as soon as http://bugs.python.org/issue29523 for rawhide and the magic
number issue for the stable ones are resolved.
Regards,
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
Hi!
On the last FESCo meeting while discussing the sudo pip Fedora [Change],
maxamillion proposed that it might be useful to issue a warning when a
user tries to run pip with root privileges--as in most cases it's not
what they should be doing (`pip install --user` is usually more
On Fri, 2017-02-10 at 15:28 +0100, Nick Coghlan wrote:
>
> On 8 February 2017 at 13:44, Tadej Janež wrote:
> >
> > As I see it, there are two issues when one has the aforementioned
> > three
> > way combination:
> >
> > 1) Users will probably use 'pip install foo' inside the
On Fri, 2017-02-10 at 09:34 -0500, Donald Stufft wrote:
>
> It’s not a Fedora bug really, it’s a venv bug, virtualenv has special
> logic to
> ensure pip actually gets installed with system site packages and when
> we
> Implemented that in venv I forgot to do it. It looks like it’s
> already been
On 8 February 2017 at 13:44, Tadej Janež wrote:
> Nick,
>
> thanks for your thorough answer.
>
> On Mon, 2017-02-06 at 20:07 +0100, Nick Coghlan wrote:
>>
>> It's not specific to Fedora's Python 3 packaging as such, but it *is*
>> specific to:
>>
>> - using --system-site-packages
Sorry, missed replying to the second part of your message.
On 8 February 2017 at 13:44, Tadej Janež wrote:
> As I see it, there are two issues when one has the aforementioned three
> way combination:
>
> 1) Users will probably use 'pip install foo' inside the activated
> virtual