-
Notifications
You must be signed in to change notification settings - Fork 46
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
Even in new setuptools I get this error: Unknown distribution option: 'long_description_content_type' #4
Comments
You need to provide it with a command, like Take a look at https://packaging.python.org/tutorials/distributing-packages/#packaging-your-project for more guidance. |
@di Could you re-open this issue? I've edited the main issue to make it clear that even when I run
|
@Flimm Are you following my guide at https://dustingram.com/articles/2018/03/16/markdown-descriptions-on-pypi? I think this error is because you are not actually using from setuptools import setup at the top of the file. |
I cloned this repo. This repo does have the line |
@Flimm What's the result of running |
@Flimm Ah, sorry. I'm remembering now that |
Thanks. I might submit a bug report to |
@Flimm It wouldn't be an appropriate bug report for I think generally the idea with Here's this project on PyPI: https://pypi.org/project/markdown-description-example/ |
Could your blog post mention that this warning is expected and does not indicate a problem? https://dustingram.com/articles/2018/03/16/markdown-descriptions-on-pypi This is a valid bug, so hopefully either Python or |
Done: di/di.github.io@b5adc2a |
I encountered this error. For posterity, it went away after I updated |
Already documented :)
https://dustingram.com/articles/2018/03/16/markdown-descriptions-on-pypi/ |
I cloned this repo, created a new virtualenv, and made sure to upgrade
setuptools
:And yet when I run
python setup.py
, I get this warning or error:Is this normal? Is the warning meant to be there? Why doesn't the new version of
setuptools
seem to supportlong_description_content_type
?The text was updated successfully, but these errors were encountered: