Work around setuptools license file metadata issue #666
+4
−0
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
gabrieldemarmiesse
merged commit c3b82f3
into
gabrieldemarmiesse:master
21 checks passed
|
Thanks, I hope it works! I'll trigger another release tonight and follow more closely. My bad really, I've been focusing a lot on work these last few weeks |
|
The fix worked! Thanks a lot @rcwbr !!! |
|
No worries at all, happy to help! |
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.
The latest 0.75.0 release failed to publish to PyPi. This appears to be a known behavior of setuptools/uv due to a change to supported metadata.
This change implements a suggested workaround, and worked for me when testing.
It appeared to keep the correct license metadata on PyPi, since this field seems to be an optional addition to the
project.license.filefield.Happy to implement any feedback, please lmk!