Skip to content
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 install milkman fails with "[ERROR] Cannot find file specified as long_description" #30

Open
davidwtbuxton opened this issue Feb 10, 2014 · 5 comments

Comments

@davidwtbuxton
Copy link

Installing the current milkman from pypi with pip install milkman (version 0.5) fails with the message:

[ERROR] Cannot find file specified as ``long_description`` (/Users/david/virtualenvpath/build/milkman/docs/index.txt)

This is cos the source distribution does not include the docs and the setup.py script chooses to fail.

This should be changed either to include the description file or to allow it to be missing. Also the license description in setup.py has changed to BSD, and the *.egg-info directory created by the distribution script gets included in the source distribution.

@jsaz
Copy link

jsaz commented Feb 2, 2015

@ccollins , this issue is still happening, more than a year after a patch was submitted. Any chance you could merge it and publish to PyPI, please?

@rpatterson
Copy link

This is affecting me to. Not sure about @davidwtbuxton's fork because it has a lot more than just the fix for this. It sure looks to me like whoever did the 0.5 release just didn't have setuptools-git installed:

https://pypi.python.org/pypi/setuptools-git

And so non-python files weren't included. If someone could just bump the version and do a release with setuptools-git installed it would probably fix this. I'd be happy to do that if someone would give me release rights on PyPI.

@rpatterson
Copy link

I confirmed that doing 'python setup.py sdist' using a python with setuptools-git installed produces a tarball that does include the missing file.

@rpatterson
Copy link

Bump? This bug means I have to do some non-typical dependency stuff for every project.

@rpatterson
Copy link

I've worked around this by uploading my own 0.5.1 release and added it's URL to pip's or easy_install's find-links.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants