Fix README.rst syntax #382
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GH action to publish a new release to PyPi failed with:
ERROR `long_description` has syntax errors in markup and would not be
rendered on PyPI.
line 365: Warning: Literal block ends without a blank line; unexpected
unindent.
Add the empty line at the end of the literal block.
Also adjust the length of the underlining for the title above, it does
not seem to count as a syntax error, but is consistent with the rest
of the README.
bugant
approved these changes
Mar 22, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GH action to publish a new release to PyPi failed with:
ERROR
long_descriptionhas syntax errors in markup and would not berendered on PyPI.
line 365: Warning: Literal block ends without a blank line; unexpected
unindent.
Add the empty line at the end of the literal block.
Also adjust the length of the underlining for the title above, it does not seem to count as a syntax error, but is consistent with the rest of the README.
About this change: What it does, why it matters
(all contributors please complete this section, including maintainers)