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

Convert README.rst to Markdown #266

Open
hydrosquall opened this issue May 5, 2019 · 4 comments
Open

Convert README.rst to Markdown #266

hydrosquall opened this issue May 5, 2019 · 4 comments

Comments

@hydrosquall
Copy link
Owner

RST is harder to work with and shrinking in usage. If we can confirm that markdown works well for the pieces that depend on it (sphinx docs, Python Package warehouse), the project documentation will be easier to maintain. It will also make adhering to projects like the all-contributors specification easier.

https://github.com/all-contributors/all-contributors

@hootnot
Copy link

hootnot commented May 7, 2019

If you stick with RST you should change the header from:

=============
Tiingo Python
=============

to:

Tiingo Python
=============

then pypi.org will render the README.rst correct

@hydrosquall
Copy link
Owner Author

hydrosquall commented May 8, 2019 via email

@hootnot
Copy link

hootnot commented May 8, 2019

Hi, pls. make the change yourself and bundle it with your deploy for the weekend.
You should also check all other headers for the length of '-' or other valid header markup characters.

I'm not sure if these would break the rendering, but the specs say the length should be equal.

Cheers

hydrosquall added a commit that referenced this issue May 9, 2019
Syntax cleanup from #266
@hydrosquall
Copy link
Owner Author

By default, an upload's description will render with reStructuredText. If the description is in an alternate format like Markdown, a package may set the long_description_content_type in setup.py to the alternate format.

Learned today that this can be linted using the readme_renderer, via twine check dist/*. The last remaining linting issue was to ensure that every underline is at least as long as the preceding line.

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

No branches or pull requests

2 participants