<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div>On May 2, 2013, at 7:17 PM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><p dir="ltr"><br>
On 3 May 2013 09:08, "Donald Stufft" <<a href="mailto:donald@stufft.io">donald@stufft.io</a>> wrote:<br>
><br>
> On May 2, 2013, at 6:48 PM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:<br>
>><br>
>> "pip --user" manipulates the per-user directories (and I believe I filed a ticket a while back suggesting it should migrate to the model distil now uses).<br>
>><br>
>> Cheers,<br>
>> Nick.<br>
><br>
> I don't think it makes sense for pip to do this tbh.</p>
<p dir="ltr">Language level installers should leave "/usr" alone by default, as that part of the filesystem is the domain of system packages.</p>
<p dir="ltr">Cheers,<br>
Nick.<br>
</p>
</div></blockquote>Out of the three primary OSs only one of them has a concept of system packages. Regardless it's a major change in behavior and isn't a clear cut right or wrong choice. It's going to need a stronger justification than that to break backwards compatibility in such a large way. </body></html>