Please clarify “Python Software Foundation License” status

[musicinmybrain]

While the text of the LICENSE file is a standard MIT license, setup.cfg claims the “Python Software Foundation License” also applies.

keyring/setup.cfg

Lines 13 to 14 in 2354d68

	License :: OSI Approved :: Python Software Foundation License
	License :: OSI Approved :: MIT License

Could you please clarify the following?

• Does this license actually apply to keyring, either to the whole package or to some part of its sources?
• If the license applies, is it in addition to the MIT license (AND), or as an alternative license (dual-licensed, OR)?
• If the license applies, is the intended license text PSF-2.0?

Ideally, these could be clarified somewhere in the sources rather than only in this issue.

Thanks!

[jaraco]

The reason the license is present is there was originally an intention to eventually migrate this library to the Python stdlib, so by dual licensing, it would be trivial to expose the same functionality under Python's license. It's my understanding that the PSF license isn't valid for projects other than Python, so only the MIT license is relevant currently.

When I proposed recently to port this to stdlib, it was dismissed, so I'm no longer anticipating contributing this to Python.

I'm going to just drop the license and keep it simple.

[musicinmybrain]

Thanks for the explanation; that’s quite helpful.