Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...
- To: Ant Dude <ant@zimage.com>
- Cc: debian-python@lists.debian.org
- Subject: Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...
- From: Brian May <bam@debian.org>
- Date: Sat, 02 Jan 2016 10:32:50 +1100
- Message-id: <[🔎] 87r3i0q3j1.fsf@prune.linuxpenguins.xyz>
- In-reply-to: <20151230095411.GA13869@beta.zimage.com>
- References: <56830BEC.60501@earthlink.net> <87wprwp9w3.fsf@prune.linuxpenguins.xyz> <20151230095411.GA13869@beta.zimage.com>
Ant Dude <ant@zimage.com> writes:
>> In short, it isn't recommended practise to use pip install with Debian,
>> except for inside a virtualenv (or similar), as the packages can
>> conflict with Debian packages - especially after a upgrade.
>
> Interesting. I did find a fix and it seems like others had the same
> problem. FFrom Debian's forum, it said
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744145#31 -- rm -rf
> /usr/local/lib/python2.7/dist-packages/requests* I renamed request
> directory and now can run Debian's pip command. Sheesh. I also notice it
> is an old bug that is still not fixed. :(
Are you sure? This bug was supposedly fixed in the Jessie version...
--
Brian May <bam@debian.org>
Reply to: