📄 Add MIT-0 license #40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/add-license"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds a license — the repo had none. Uses MIT-0 (MIT No Attribution): as permissive as MIT but with no attribution requirement, while keeping a warranty disclaimer that is valid across jurisdictions (unlike a public-domain dedication such as The Unlicense, whose validity is doubtful under French/EU law where the author is based).
Changes
LICENSE— canonical SPDX MIT-0 text, © 2024 Matéo Greil.pyproject.toml— declare the license via PEP 639:license = "MIT-0"+license-files = ["LICENSE"], and bump the build backend tosetuptools>=77(needed for SPDX license-expression support). No license Trove classifier is added (PEP 639 forbids mixing the two).Verification
python -m buildemitsLicense-Expression: MIT-0andLicense-File: LICENSEin the wheel METADATA;LICENSEis bundled in both wheel (dist-info/licenses/) and sdist.pytest: 89 passed.mypy: no issues.Opened as draft (WIP) — remove the
WIP:prefix to mark ready.Rationale discussed: MIT-0 chosen over 0BSD for ecosystem familiarity (Python is MIT-heavy), over The Unlicense for legal robustness in France, over plain MIT because attribution wasn't wanted.
WIP: 📄 Add MIT-0 licenseto 📄 Add MIT-0 license