Conversation
|
Note-to-self, use https://pypi.org/project/trove-classifiers/ instead of packaging-classifiers. |
|
Hi Ben! Thanks for the PR! I'm so sorry I didn't see this when it was fresh. My hope is that this a low-deps way to classify ~80% of real-world projects, with the remainder just returning SPDX is fantastic as a repository of known licenses, I agree. I think it's a lot of complexity aimed at getting those last few percent, which tbh you can get with licensedcode today, especially if you're interested in more fuzzy matches. If you're interested in having a non-nexB solution for this, I'd recommend forking and calling it infer-license-full or so. I'd like to keep this small for the time being. |
This PR extends the list of licenses using the text folder of spdx/license-list-data.
I've used our dependency fetching tool dfetch, since I only needed the "text" dir and adding the entire spdx-license repo seemed overkill. This added the
dfetch.yamlmanifest and.dfetch_data.yamlfiles. I can remove them if you like.To check all the trove classifiers are valid and covered, I've added 2 tests that use packaging-classifiers to match the
KNOWN_LICENSESlist and all available classifiers mentioningLicense ::both ways.Open questions
KNOWN_LICENSES, this leads to some duplication, should I merge your existing list of licenses?