Improvements to PyPI packaging #2
Open
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
The new version of PyPI and Warehouse added support for PEP 566, which adds the option "long_description_content_type" to specify the format of the long description used on the PyPI page. This removes the need to convert it to RST using pypandoc.
# 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.
The new version of PyPI and Warehouse added support for PEP 566,
which adds the option "long_description_content_type" to specify the
format of the long description used on the PyPI page. This removes
the need to convert it to RST using pypandoc, which (for this package
at least) was not formatting correctly.
Summary:
Remove need to convert README to RST
Ensure LICENSE gets included in the package
I'm opening similar PRs (well, almost identical) in hug_explainable and hug_yaml as well. Apologies for the notification spam!