readme_renderer
readme_renderer copied to clipboard
Safely render long_description/README files in Warehouse
This is the same as my PR https://github.com/github/markup/pull/1452 and it _may_ make sense to incorporate other changes from GitHub's rST processing.
I have just tried to upload a new version of one of my projects and encountered the `The project's long_description has invalid markup which will not be rendered on PyPI`...
Such relative URLs will not work correctly when displayed on PyPI.
**What's the problem this feature will solve?** It is very easy to come across packages in Warehouse which have rst descriptions that are wrongfully rendered as plain text. I believe...
As reported in: https://github.com/pypa/twine/issues/1102 `twine check` fails when parsing the `readme` file contains badges. If one of the badge has a scale factor, the `readme_renderer` fails claiming it is not...
While trying to [verify](https://joinmastodon.org/verification) a link from a Mastodon instance to a Mailman Postorius mailing list profile, I found that the rel="me" attribute on the reciprocal link back to Mastodon...
The alerts that display on the main page of the repository are not displaying properly on PyPI GitHub: https://github.com/tektronix/tm_devices PyPI: https://pypi.org/project/tm-devices/
When the `README.rst` file contains RST [definition lists](https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#definition-lists), which requires a space **before** the colon, like term : classifier Definition They are rendered by PyPi without the colon and spaces,...
As gitpod's moved to no longer cloud-based environments, and supports using the devcontainer standard, use that instead to support GitHub Codespaces.
closes #323