R. David Murray <rdmur...@bitdance.com> added the comment: The LICENSE.txt file is "just" the Python license, which has a rather convoluted history. Newer contributions are all under an Apache-style license from the individual contributors. My understanding (but I'm not a lawyer) is that everything in the distribution has been vetted as available for use under the LISCENSE.txt, which includes commercial use. If you believe that the language either in that file or on the web site does not convey that legally, then p...@python.org is who you need to contact. On the development side, the most we can do is update a license if someone figures out that it is appropriate to do so.
For the website text, there's a mailing list listed on the mail.python.org page. There's a project ongoing to make updating the web site easier, but currently there aren't very many developers who do web site updates, and such updates are not tracked on this tracker, just on that mailing list. (Yes, this is not ideal, but it is where we are at right now.) I've added one of those devs as nosy, perhaps he will have additional comments. ---------- nosy: +michael.foord title: Berkeley DB License conditions are onerous (and poorly documented) -> Is LICENSES.txt up to date? _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14759> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
