-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update License Info with Well-known OSA MIT License Classifier #857
Conversation
Update license data in ``pyproject.toml``, replacing ``license`` property with a ``classifiers`` item for the OSA MIT license.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
There's also the |
i guess this means since we're using MIT the classifier is the way to go |
I don't think they're mutually exclusive; I use both in my project (usually BSD though). Big guys like |
The reason for the change was that the I doubt having both in place would cause problems, but the documentation (which you linked) does state that you should use
|
Per PEP 639, both [project]
license = "MIT" |
thanks for the info guys, i think i'll just leave it as is for now |
I am currently unable to utilize
basedpyright
at my place of work because the (industry-standard) managed system we use to procure external code can not identify the license type.This change replaces the current license property with the registered classifier for the MIT License, ensuring that it will be parsed properly by managed procurement tools like ours.
pyproject.toml
, replacinglicense
property withclassifiers
, containing theLicense :: OSI Approved :: MIT License
classifier, and Python version classifiers from3.8
–3.13
.