docs: clarify LGPL-2.1-or-later license in README#1763
Merged
Conversation
The COPYING file ships the verbatim text of LGPL 2.1, while the package metadata in pyproject.toml declares the SPDX identifier LGPL-2.1-or-later. License-detection tools that read pyproject.toml report the project as 'or later', but the README only said 'LGPL, see COPYING file for details', leaving downstream consumers unsure which version applies. State the 'or later' grant explicitly in the README so the README, COPYING, and pyproject.toml agree on a single, machine- and human-readable answer.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1763 +/- ##
=======================================
Coverage 99.77% 99.77%
=======================================
Files 33 33
Lines 3500 3500
Branches 490 490
=======================================
Hits 3492 3492
Misses 5 5
Partials 3 3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
bdraco
approved these changes
May 20, 2026
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.
Summary
The COPYING file ships the verbatim text of LGPL 2.1, but
pyproject.tomldeclares the SPDX identifierLGPL-2.1-or-later. License-detection tools (e.g. LicenseCheck) report the project as "or later" while the README only said "LGPL, see COPYING file for details", leaving downstream consumers unsure which version applies.This change states the "or later" grant explicitly in the README so the README, COPYING, and
pyproject.tomlagree.Fixes #1600
Changes
LGPL-2.1-or-laterstatement that cites COPYING andpyproject.toml.Test plan
pyproject.tomllicense = "LGPL-2.1-or-later"unchanged — README now matches.Generated by Kōan /fix
Quality Report
Changes: 1 file changed, 7 insertions(+), 1 deletion(-)
Code scan: clean
Tests: passed (4 PASSED)
Branch hygiene: clean
Generated by Kōan post-mission quality pipeline