Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10

2020-02-24 Thread Robin Gustafsson
Hi,

I've seen this before and I'm fairly sure that it's an issue from the
system version of pip interacting badly with a pip-installed version
of pip. However, I also cannot reproduce it now.

It has been discussed upstream [1] and a compatibility layer has been
added to avoid it [2][3]. That may explain why it is seemingly
unreproducible now.

Instead of the error, I'm now receiving this when running a newer
pip-installed version through the system-installed version:

WARNING: pip is being invoked by an old script wrapper. This will
fail in a future version of pip.
Please see https://github.com/pypa/pip/issues/5599 for advice on
fixing the underlying issue.
To avoid this problem you can invoke Python with '-m pip' instead
of running pip directly.

All in all, I think the error in this bug is likely not caused by the
packaged version itself. The wrapper should probably be changed at
some point, though.

[1] https://github.com/pypa/pip/issues/5599
[2] https://github.com/pypa/pip/issues/7498
[3] https://github.com/pypa/pip/commit/3f4bb75

Regards,
Robin



Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10

2020-01-26 Thread Joan Luc Labòrda
I did use the system python command, it was a pip 9 version and i hacked 
it by changing the line "from pip._internal import main" to "from pip 
import main" then i could upgrade to pip 20.0.1 and now it works fine


Le 25/01/2020 à 23:56, Andreas Beckmann a écrit :

Control: tag -1 = moreinfo unreproducible

On Fri, 24 Jan 2020 10:17:34 +0100 joanluc
 wrote:

When invoking `usr/bin/pip' with any command of it, the program crashes with
the message :
"Traceback (most recent call last):
   File "/usr/bin/pip", line 9, in 
 from pip._internal import main
ImportError: No module named _internal"

Hi,

I cannot reproduce this. The pip._internal module should be located at
/usr/lib/python2.7/dist-packages/pip/_internal/*
Are there any local environment variables on your system that alter the
python search path?
Are you using the system python command or do you have a "special"
python installation?
Is anything corrupted? (e.g. check with debsums)


Andreas


--
Jean-Luc LABORDE (Joan-Luc Labòrda)
CoFo CRPP 0556.84.30.13



Bug#949733: [Python-modules-team] Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10

2020-01-25 Thread Emmanuel Arias
Hi,

I had similar issues, when I didn't clean the environment, e.g. I had
a .local/lib/python2.7/site-packages

When I removed that folder, I was not have problems with python-pip

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

El sáb., 25 de ene. de 2020 a la(s) 20:00, Andreas Beckmann
(a...@debian.org) escribió:
>
> Control: tag -1 = moreinfo unreproducible
>
> On Fri, 24 Jan 2020 10:17:34 +0100 joanluc
>  wrote:
> > When invoking `usr/bin/pip' with any command of it, the program crashes with
> > the message :
> > "Traceback (most recent call last):
> >   File "/usr/bin/pip", line 9, in 
> > from pip._internal import main
> > ImportError: No module named _internal"
>
> Hi,
>
> I cannot reproduce this. The pip._internal module should be located at
> /usr/lib/python2.7/dist-packages/pip/_internal/*
> Are there any local environment variables on your system that alter the
> python search path?
> Are you using the system python command or do you have a "special"
> python installation?
> Is anything corrupted? (e.g. check with debsums)
>
>
> Andreas
>
> ___
> Python-modules-team mailing list
> python-modules-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team



Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10

2020-01-25 Thread Andreas Beckmann
Control: tag -1 = moreinfo unreproducible

On Fri, 24 Jan 2020 10:17:34 +0100 joanluc
 wrote:
> When invoking `usr/bin/pip' with any command of it, the program crashes with
> the message :
> "Traceback (most recent call last):
>   File "/usr/bin/pip", line 9, in 
> from pip._internal import main
> ImportError: No module named _internal"

Hi,

I cannot reproduce this. The pip._internal module should be located at
/usr/lib/python2.7/dist-packages/pip/_internal/*
Are there any local environment variables on your system that alter the
python search path?
Are you using the system python command or do you have a "special"
python installation?
Is anything corrupted? (e.g. check with debsums)


Andreas



Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10

2020-01-24 Thread joanluc
Package: python-pip
Version: 18.1-5
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

When invoking `usr/bin/pip' with any command of it, the program crashes with
the message :
"Traceback (most recent call last):
  File "/usr/bin/pip", line 9, in 
from pip._internal import main
ImportError: No module named _internal"

I tried making a workaround by replacing the line
"from pip._internal import main" by "from pip import main" in '/usr/bin/pip'
but it did crash after having downloaded the module.



-- System Information:
Debian Release: bullseye/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-2-amd64 (SMP w/16 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python-pip depends on:
ii  ca-certificates  20190110
ii  python   2.7.17-2
ii  python-pip-whl   18.1-5

Versions of packages python-pip recommends:
ii  build-essential12.8
ii  python-all-dev 2.7.17-2
ii  python-setuptools  44.0.0-1
ii  python-wheel   0.33.6-2

python-pip suggests no packages.

-- no debconf information