-
Notifications
You must be signed in to change notification settings - Fork 251
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
Add SPDX license data #799
Conversation
4ab216d
to
3d8d9af
Compare
I've got one suggestion: The PEP specifies that the supported SPDX license list is The code looks straightforward to me and it works fine. I wonder whether this should be a job running on every PR or only a part of the build path? Side note: the other task, pep440, doesn't seem to work anymore. I'll open an issue. |
Per feedback, integrate a variant of pypa#799 that builds a minimal JSON dataset to feed vendored license-expression 32K src/packaging/_spdx.json vs 848K src/packaging/_vendor/license_expression/data/scancode-licensedb-index.json
Per feedback, integrate a variant of pypa#799 that builds a minimal JSON dataset to feed vendored license-expression 32K src/packaging/_spdx.json vs 848K src/packaging/_vendor/license_expression/data/scancode-licensedb-index.json
Per feedback, integrate a variant of pypa#799 that builds a minimal JSON dataset to feed vendored license-expression 32K src/packaging/_spdx.json vs 848K src/packaging/_vendor/license_expression/data/scancode-licensedb-index.json
Superseded by #828 |
In response to this comment by a maintainer expressing approval for license parsing functionality, this PR introduces an invoke task to update an enumeration encoded as a Python structure.
This setup is the same as what Hatchling does:
The parser itself and what the API should look like will be discussed in a separate PR.
The file may be generated by running:
invoke licenses.update