Add long_description_content_type to sdist setup kwargs #1166
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
|
Thanks for contributing! Would you be able to rebase this into one commit? |
|
Yes certainly :-) |
steinnes
force-pushed
the
include-long-desc-content-type-in-sdist
branch
from
8c359f6
to
79af8cc
Compare
steinnes
force-pushed
the
include-long-desc-content-type-in-sdist
branch
from
79af8cc
to
c3d7706
Compare
|
We just encountered this behavior too. |
|
Superseded by #1994 |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR attempts to add the content type of long_description to setup.py kwargs when building sdists.
I noticed that the content type is included in the wheel metadata, but missing from the setup() call in sdist packages.
I did not update any documentation as part of this pull request, because I do not believe this is a change/feature requiring documentation, rather a minor bugfix.