Based on discussions on IRC, we have a patch for pip 6.0 that I've backported
to the Debian packaged version. I believe it does the right thing now:
# pip install requests
Requirement already satisfied (use --upgrade to upgrade): requests in
IMO we should patch pip to *not* touch (install, upgrade, uninstall,
etc.) anything in /usr directory (or /) except /usr/local. Our Python
interpreter already installs to /usr/local and so should pip.
This way:
* pip doesn't need to figure out which file can be touched,
* we can detect cause of
On Dec 03, 2014, at 03:20 PM, Piotr Ożarowski wrote:
IMO we should patch pip to *not* touch (install, upgrade, uninstall,
etc.) anything in /usr directory (or /) except /usr/local. Our Python
interpreter already installs to /usr/local and so should pip.
+1
This way:
* pip doesn't need to
Quoting Matthias Klose d...@debian.org:
For jessie I suggest to just disable pip when used on the system
python, unless a new option
--yes-i-want-to-screw-up-my-system-python is given.
How about disabling pip for uid 0 altogether?
___
I'd very much prefer it if you didn't do this. This *is* going to break things
for people and it's going to cause a bunch of confusion.
---
Donald Stufft
PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
___
Python-modules-team mailing list
On 12/02/2014 10:38 PM, Scott Kitterman wrote:
On Tuesday, December 02, 2014 19:28:20 Donald Stufft wrote:
So what if Debian just patched python-pip so that it doesn’t remove the
files from /usr/lib (but it would remove files from /usr/local etc). This
would have the effect of pip not touching
6 matches
Mail list logo
