Relax licence restrictions to support custom licences #2202
Conversation
This change adds support of use of custom licenses for projects. If the value specified for `licence` is not in the SPDX License List or "Proprietary", we treat it as a custom licence withe value (as is) as the name. As a side-effect, the validation of licence is no longer performed when executing `poetry check`. Resolves: python-poetry#2020
|
This is probably the simplest change to support custom licences. The main reservation I had was that now, if someone makes a typo (eg: |
Maybe a simple distance measure could be used to catch such typos. |
|
I feel it might be adding unnecessarily complexity without much guaretee in return. And, personally, I do not think the impact of a typo in the licence warrants such a safegueard. Besides, this can be added in later if we really need it. |
|
This might need to move to https://github.com/python-poetry/core I think. |
|
This has now been split into two PRs.
The documentation fix for (2) will be created if/when the version of poetry-core is merged. |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This change adds support of use of custom licenses for projects. If the
value specified for
licenceis not in the SPDX License List or"Proprietary", we treat it as a custom licence withe value (as is) as
the name.
As a side-effect, the validation of licence is no longer performed when
executing
poetry check.Resolves: #2020 #2198
Pull Request Check List