-
-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package multiple license files in .dist-info #861
Labels
enhancement
New feature or request
Comments
Thanks for the issue, feel free to implement it and send PRs. |
@messense I have created a PR for Adding license_expression and license_files serialization to support this work in the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Add support for
license-files
option in metadata for PEP 639 so that licenses are added to the.dist-info
wheel folder. This extends the work of #837 (#829).There are three separate pieces covered here:
license-files.paths
license-files.globs
I think a minimum version of this feature with the highest return would be to add the convention for automatically including license files with the
license-files
option being treated as dynamic to trigger the default behavior. I have a working spike of the implementation but I need to write tests.Looking through the code, we'd need to add
license-files
to the pyproject-toml-rs project to deal with serializing the new metadata option to unblock support forlicense-files.(paths|globs)
which can build on the work done in #837 to append the license files to the merging metadata.Current State
The single license specified in the
pyproject.toml
will be copied into the.dist-info
wheel folder:Desired State
The link used for multiple file use in #837 is broken (and in the code). The advanced example for PEP 639 shows the use of
license-files.paths
orlicense-files.globs
for listing multiple licenses:Example with notice:
Multiple license files:
Or alternatively, matched via glob patterns:
PEP 649 - I maintain an existing package that’s already licensed gives further defaults used by
setuptools
for automatically including these files.The text was updated successfully, but these errors were encountered: