Your message dated Sat, 14 Mar 2020 19:34:56 -0400
with message-id <2113783.URg3d3lheC@l5580>
and subject line Closing - probably local configuration error
has caused the Debian Bug report #949733,
regarding python-pip: 'pip install' don't work for python2 in Debian10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
949733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 <module>
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-essential 12.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
--- End Message ---
--- Begin Message ---
I have just tried using pip with python2 in a clean, minimal chroot and do not
have this error. All the feedback so far indicates that similar issues have
been associated with non-system modules in the path. Given the inability to
reproduce this and other people's feedback, I think it's reasonably clear this
is not a Debian package bug.
If you are still having problems, you should seek support through normal
Debian support channels.
Scott K
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
