Make pyproject.toml PEP639 compliant#36
Merged
mlucool merged 1 commit intodeshaw:mainfrom Apr 6, 2026
Merged
Conversation
mlucool
approved these changes
Apr 6, 2026
peytondmurray
force-pushed
the
pep639-compliance
branch
from
bbb658e to
38b9dc8
Compare
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.
Follow on from #28 - according to https://packaging.python.org/en/latest/specifications/pyproject-toml/#license the
licensefield needs to be a string, andlicense-filesis where we should be putting license file paths. After discussing with colleagues, it seems PEP639-compliance will result in the license expression being shown on the PyPI page for this project. Closes #27.