Adopt PEP 639 license statement in pyproject.toml #26
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.
Hi,
thanks for the bindings 🙂 !
recently I scanned a virtual environment of mine and found that loro-py was the only package among 80 or so that showed up with license: UNKNOWN when running something like
$ pip-licenses --from=mixed --format=rst.I guess this is due to
license = { file = "LICENSE" }being the only license info in pyproject.toml. The license file gets copied to the wheel, but no meta-information is provided.I suggest to follow https://packaging.python.org/en/latest/specifications/pyproject-toml
-- Lukas