[Python-modules-team] Bug#956332: python-pip: Binary package python-pip (for Python 2) is no longer being built from the python-pip source package.

[Justin Searle]

Source: python-pip
Version: 20.0.2-4
Severity: critical
Tags: a11y
Justification: breaks unrelated software

Dear Maintainer,

During a recent apt upgrade, there was conflict reported for binary
pacakge python-pip.  It's dependancy "python-pip-whl = 18.1-5" was no
longer being met.  Apparently python-pip-whl had been upgraded to
20.0.2-4, but python-pip was left behind at version 18.1-5.  Looking
futher into this, is seems like both these packages were builing built
from the source package python-pip, but the latest binary version of 
python-pip was not longer being built from the latest python-pip source
package.

I understand that python2 is planned for removal, however as long as we
have the python 2 interpter available, I think we need to keep the
python-pip package available as well.  Otherwise, if it is auto-removed
by apt because of the broken dependency of python-pip-whl, then all
non-debian package and hand installed pip packages become broken.


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

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