Update LICENSE to PEP639 standards
@thomasrockhu-codecov is already working on this.
Since Jan 27, 2025.
- Dominant language
- Python
- Stars
- 89
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Now that PEP 639 has finally landed in full, it's best to use separate license SPDX and license-files: https://packaging.python.org/en/latest/specifications/pyproject-toml/#license.
setuptools hasn't yet implemented it, however:
https://github.com/pypa/setuptools/issues/4629
https://github.com/pypa/setuptools/issues/3596
https://github.com/pypa/setuptools/issues/4759
https://github.com/pypa/setuptools/pull/4706
https://github.com/pypa/setuptools/pull/4728
So this is something to do in the future. For now, it would be a good idea to add a TODO code comment, so this action item is not lost.
see (comment)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.