Package: python-pip-whl Version: 9.0.1-2 Severity: normal Dear Maintainer,
When I run pip freez in a new venv, I'm getting "pkg-resources==0.0.0". Here's how I reproduce it: $ python3 --version Python 3.5.3 $ python3 -m venv /tmp/pip-freeze $ . /tmp/pip-freeze/bin/activate (pip-freeze) $ python3 -m pip --version pip 9.0.1 from /tmp/pip-freeze/lib/python3.5/site-packages (python 3.5) (pip-freeze) $ python3 -m pip freeze pkg-resources==0.0.0 I found this bug already reported here: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1635463 and I also opened an issue here: https://github.com/pypa/pip/issues/4668/. I just expected a "pip freeze" to output nothing in a newly created venv. It looks like pip freeze expect pkg_resource to be in setuptools, not packaged separately. I searched a bit and can't find why it gets separated from setuptools on Debian. I does *not* looks like a "vendorized" version of something: it looks to lie in setuptools from the beginning: https://github.com/pypa/setuptools/commit/ee8b1aa7f26f8c423c53b50bc743d8a725bbab5a -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-pip-whl depends on: ii ca-certificates 20161130+nmu1 python-pip-whl recommends no packages. python-pip-whl suggests no packages. -- no debconf information -- Julien Palard https://mdk.fr