-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pip freeze includes "pkg-resources==0.0.0" #4668
Comments
He's here, probably a venv issue more than a $ python3 -m venv pip-freez There's other wheels here, still don't know why this one is picked by pip freeze and not the others. |
This doesn't occur for me on Windows, and as far as I'm aware it's not typical for venvs to have a "share" directory containing wheels. Could this be related to how your OS vendor has packaged python/pip? (Do Debian unbundle pip's dependencies?) |
Looks like so, the Debian packaged
While the cpython 3.5 one have:
|
OK, so I guess you'll need to report this to Debian. |
I'm reading: https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1220988.html and I see:
So I checked if pkg_resource is copied from /usr/share as said and yes: $ dpkg -S /usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl So I checked python-pip-whl which contains in its README.debian:
|
OK, but not sure why they've created a separate Anyway, there's clearly no pip or virtualenv bug here, it's up to Debian to make sure their "crazy mess" is consistent ;-) Nevertheless, thanks for reporting it - it's useful to us to know what the distros do, so we can advise others in similar situations to yours. |
Issue Debian side: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871790 |
It doesn't look like there is anything for pip to do here, so I will close this issue, but please reach out if there is something pending. |
Description:
Ran pip freeze, got
pkg-resources==0.0.0
like in #4022.What I've run:
The text was updated successfully, but these errors were encountered: