Use reST format for README and LICENSE #19
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
Currently, PyPI supports only reST as markup format while GitHub can live with both markdown or reST, so it's easier to use reST. In setup.py we can now assume that README.rst exists since it is included in the source distribution via MANIFEST.in.
Its simpler to have only one markup format present in the project.
…up.cfg
Nobody wants DOS line endings. Best compare with:
git diff --ignore-space-at-eol
milibopp
added a commit
that referenced
this pull request
Nov 29, 2013
Use reST format for README and LICENSE
milibopp
added a commit
that referenced
this pull request
Jun 10, 2023
Use reST format for README and LICENSE
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Resolves #18