Open brettcannon opened 5 years ago
Related to Improving license clarity with better package metadata (discuss.python.org). The Motivation section of the associated draft PEP gives some background on why trove classifiers may be troublesome in practice to handle license questions programmatically (mostly ambiguity, from reading the linked issues).
I'm on board for doing this and I think we should wait for that PEP to get done before doing this.
What's the problem this feature will solve? To help users not use software whose license does not meet some criteria the user has.
Describe the solution you'd like A way to specify what license trove classifiers are acceptable and either warn or error out if none of the trove classifiers exist (or at least if no trove classifier for a license is specified).
Alternative Solutions Get PyPI and/or twine to complain very loudly if no license is specified. :)
Additional context Basically having to hunt this stuff down sucks, so it might be helpful to expose this more upfront when people try to use software which might not meet corporate requirements.