We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We ought to warn the user about a problem if the long_description is entirely absent from setup.py.
long_description
setup.py
Example: https://github.com/rytilahti/python-miio/blob/21065f696c2167e86d72f90e660a14dcef573587/setup.py has no long_description. But when I run readme-renderer version 17.2 in the root of that repo, in a Python 3.5.3 virtualenv, doesn't speak up about an error:
$ python setup.py check -r -s running check $
cc @rytilahti
The text was updated successfully, but these errors were encountered:
@di what's your take on this feature idea?
Sorry, something went wrong.
Sounds like a great idea.
Warn about missing long description
1577cd1
Additionally, add comprehensive tests for the disutils integration. Resolves pypa#64
Warn about missing long description (#69)
506da6a
Additionally, add comprehensive tests for the disutils integration. Resolves #64
No branches or pull requests
We ought to warn the user about a problem if the
long_description
is entirely absent fromsetup.py
.Example: https://github.com/rytilahti/python-miio/blob/21065f696c2167e86d72f90e660a14dcef573587/setup.py has no
long_description
. But when I run readme-renderer version 17.2 in the root of that repo, in a Python 3.5.3 virtualenv, doesn't speak up about an error:cc @rytilahti
The text was updated successfully, but these errors were encountered: