Re: Joining python-modules
On 01/01/16 15:44, Yuri D'Elia wrote: > I've read the policy from > https://python-modules.alioth.debian.org/policy.html and I accept it (in > fact, I love the idea behind collaborative maintenance, collab-maint, > and I subscribed to LowThresholdNmu as well). I perhaps should add that my username on alioth is wavexx-guest
Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...
Hello, sorry for the delay in my reply! On Saturday, January 02, 2016 10:32:50 AM Brian May wrote: > Are you sure? This bug was supposedly fixed in the Jessie version... 03_export-IncompleteRead.patch is still present in the requests packaging (since pip version in Debian still need it) and was shipped with requests 2.4.3-2. @Ant Dude: just to recap and to be sure I understand correctly: you should have installed requests 2.4.3-6 and python-pip (1.5.6-5), right? Renaming requests (Debian packaged version) install directory make pip work, right? Debian packaged version of pip doesn't use convenience copies, so do you have a version of requests installed not using apt? Please can you tell me what is the output of the following? python -c "import requests; print requests.__version__" Please, can you also try: python -c "from requests.compat import IncompleteRead" Thanks! -- Daniele Tricoli 'eriol' https://mornie.org signature.asc Description: This is a digitally signed message part.
Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...
On Sat, Jan 02, 2016 at 04:39:24PM +0100, Daniele Tricoli wrote:
> Hello,
> sorry for the delay in my reply!
Hi! No problems due to the holidays. ;)
> On Saturday, January 02, 2016 10:32:50 AM Brian May wrote:
> > Are you sure? This bug was supposedly fixed in the Jessie version...
>
> 03_export-IncompleteRead.patch is still present in the requests packaging
> (since pip version in Debian still need it) and was shipped with requests
> 2.4.3-2.
>
> @Ant Dude: just to recap and to be sure I understand correctly: you should
> have installed requests 2.4.3-6 and python-pip (1.5.6-5), right?
Yes, but probably from Wheezy when before Jessie became the new stable.
My dpkg -l shows:
ii python-requests 2.4.3-6
all elegant and simple HTTP library for Python2, built for human beings
ii python-pip1.5.6-5
all alternative Python package installer
> Renaming requests (Debian packaged version) install directory make pip work,
> right?
Yes.
> Debian packaged version of pip doesn't use convenience copies, so do you have
> a version of requests installed not using apt?
> Please can you tell me what is the output of the following?
>
> python -c "import requests; print requests.__version__"
>
> Please, can you also try:
>
> python -c "from requests.compat import IncompleteRead"
With /usr/local/lib/python2.7/dist-packages/requestsRENAMED
$ python -c "import requests; print requests.__version__"
2.4.3
$ python -c "from requests.compat import IncompleteRead"
$
With the original /usr/local/lib/python2.7/dist-packages/requests:
$ python -c "import requests; print requests.__version__"
2.9.1
$ python -c "from requests.compat import IncompleteRead"
Traceback (most recent call last):
File "", line 1, in
ImportError: cannot import name IncompleteRead
I tried "apt-get purge python-pip python-requests" and then reinstalling
them to see if the problem would go away. Nope:
$ pip
Traceback (most recent call last):
File "/usr/bin/pip", line 9, in
load_entry_point('pip==1.5.6', 'console_scripts', 'pip')()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 356, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2476,
in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2190,
in load
['__name__'])
File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 74, in
from pip.vcs import git, mercurial, subversion, bazaar # noqa
File "/usr/lib/python2.7/dist-packages/pip/vcs/mercurial.py", line 9,
in
from pip.download import path_to_url
File "/usr/lib/python2.7/dist-packages/pip/download.py", line 25, in
from requests.compat import IncompleteRead
ImportError: cannot import name IncompleteRead
Again, I renamed the old requests directory for me to use pip again. :(
Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...
On Sat, Jan 02, 2016 at 08:18:13AM -0800, Ant Dude wrote: > Again, I renamed the old requests directory for me to use pip again. :( Why don't you just uninstall the package you've installed manually to /usr/local? It seems to me you don't need it. -- WBR, wRAR signature.asc Description: PGP signature
Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...
Daniele Tricoli writes: > @Ant Dude: just to recap and to be sure I understand correctly: you should > have installed requests 2.4.3-6 and python-pip (1.5.6-5), right? > Renaming requests (Debian packaged version) install directory make pip work, > right? He previously said he renamed the /usr/local version, not the packaged version: /usr/local/lib/python2.7/dist-packages/requestsRENAMED I think he might be getting confused where the files are coming from and the difference between "apt-get install python-xyz" vs "pip install xyz". So I will try to explain: If you install the package with "pip install xyz" - it will get installed under /usr/local. However the Debian package system doesn't understand this, and doesn't know that you have done this. So you may have installed a version that is not compatible with the Debian packages. When you install a package with "apt-get install python-xyz" (including security updates) it will get installed under /usr/lib. The package system knows about these packages and will work to ensure that the versions are compatible. However any packages you have installed locally with "pip install xyz" in /usr/local will take priority and get used instead. Even if they are not compatible. So as a result, it is not a good idea to install any packages locally in /usr/local - you should always install packages with "apt-get" as only these packages are tested by Debian to work with Debian packages. Just to confuse matters, there are some upstream packages - particular those not yet in Debian, where the upstream authors do recommend installing missing dependancies with "pip install xyz" - this is not actually good practise. Hope this helps. -- Brian May
