pip freeze includes "pkg-resources==0.0.0" (Ubuntu Server 16.04 LTS)

[crw]

• Pip version:
  8.1.2
• Python version:
  Python 2.7.12
• Operating System:
  Linux ubuntu 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  

  Description:

pip freeze, run from a freshly created virtualenv, always includes

pkg-resources==0.0.0

When not extracted from the output when written to requirements.txt, it causes build failures on deployment when creating virtualenvs from that requirements file.

What I've run:

$ pip freeze
ago==0.0.6
bcrypt==2.0.0
beautifulsoup4==4.3.2
blinker==1.3
cffi==1.5.2
ecdsa==0.11
email==6.0.0a1
Flask==0.10.1
flatland==0.8
funcsigs==1.0.2
gunicorn==19.1.0
itsdangerous==0.24
Jinja2==2.8
MarkupSafe==0.23
mock==2.0.0
newrelic==2.4.0.4
nose2==0.6.5
pbr==1.10.0
pika==0.10.0
pkg-resources==0.0.0
pycparser==2.14
PyMySQL==0.7.9
python-dateutil==2.1
pytz==2014.4
redis==2.10.5
requests==2.11.1
six==1.10.0
SQLAlchemy==1.1.2
textile==2.3.3
Werkzeug==0.11.8

[RonnyPfannschmidt]

this is a bug caused by ubuntu - they should fix it, they lied about metadata

[crw]

Thanks, I opened an issue with Ubuntu: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1635463

[das-g]

this is a bug caused by ubuntu - they should fix it, they lied about metadata

Can you go into more detail (best in a comment on the bug report on launchpad, I guess) about what is different and/or wrong in Ubuntu, causing this behavior? (E.g. what metadata is affected and how?)

[RonnyPfannschmidt]

@das-g they created a package metadata item with a bad version that shouldn't exist

[moha-abdul]

I you still have the error even after removing the pkg-resources=0.0.0, run the basic git add and git commit commands then push to heroku
git add .
git commit -m "remove pkg-resource"
git push heroku master

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.