> On Feb 16, 2016, at 4:10 PM, Glyph Lefkowitz <gl...@twistedmatrix.com> wrote:
> 
>> 
>> On Feb 16, 2016, at 3:05 AM, Matthias Klose <d...@ubuntu.com> wrote:
>> 
>> On 02.02.2016 02:35, Glyph Lefkowitz wrote:
>>> 
>>>> On Feb 1, 2016, at 3:37 PM, Matthias Klose <d...@ubuntu.com> wrote:
>>>> 
>>>> On 30.01.2016 00:29, Nathaniel Smith wrote:
>>>>> Hi all,
>>>>> 
>>>>> I think this is ready for pronouncement now -- thanks to everyone for
>>>>> all their feedback over the last few weeks!
>>>> 
>>>> I don't think so.  I am biased because I'm the maintainer for Python in 
>>>> Debian/Ubuntu.  So I would like to have some feedback from maintainers of 
>>>> Python in other Linux distributions (Nick, no, you're not one of these).
>>> 
>>> Possibly, but it would be very helpful for such maintainers to limit their 
>>> critique to "in what scenarios will this fail for users" and not have the 
>>> whole peanut gallery chiming in with "well on _my_ platform we would have 
>>> done it _this_ way".
>>> 
>>> I respect what you've done for Debian and Ubuntu, Matthias, and I use the 
>>> heck out of that work, but honestly this whole message just comes across as 
>>> sour grapes that someone didn't pick a super-old Debian instead of a 
>>> super-old Red Hat.  I don't think it's promoting any progress.
>> 
>> You may call this sour grapes, but in the light of people installing
>> these wheels to replace/upgrade system installed eggs, it becomes an issue. 
>> It's fine to use such wheels in a virtual environment, however people tell 
>> users to use these wheels to replace system installed packages, distros will 
>> have a problem identifying issues.
> 
> I am 100% on board with telling people "don't use `sudo pip install´".  
> Frankly I have been telling the pip developers to just break this for years 
> (see https://pip2014.com, which, much to my chagrin, still exists); `sudo pip 
> install´ should just exit immediately with an error; to the extent that 
> packagers need it, the only invocation that should work should be `sudo pip 
> install --i-am-building-an-operating-system´.

As someone that handles the tooling side, I don't care how it works as long as 
there is an override for tooling a la Chef/Puppet. For stuff like Supervisord, 
it is usually the least broken path to install the code globally.

--Noah

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Reply via email to