Fix Python publishing metadata#72
Merged
Merged
Conversation
Benjscho
approved these changes
Jan 30, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 fixes a few metadata issues for the Python packages in this project, to ensure the data shown on PyPI during publishing is correct.
Currently:
LICENSEfile doesn't existREADME.mdfile is not being published for Django (as can be seen in 0.4.0)README.mdin a way that requires full URLs which are hard to maintain and easy to mess upThe change here fixes the licenses for all projects, and uses a hook to update local paths to fully qualified links which will work when clicked from PyPI. The local paths are easier to maintain in the repo, and will work for people with cloned copies in an IDE.
This is conceptually similar to awslabs/aurora-dsql-tortoise-orm#24 but I used a community plugin since I couldn't figure out a simple way to share the hook across the 3 Python packages and didn't want to duplicate the hook code. That is always an option in the future if we can figure out the build issues with parent path references and want to switch.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.