This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jeff.Laing
Recipients Jeff.Laing, docs@python, r.david.murray
Date 2012-05-09.02:06:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1336529181.09.0.842581998436.issue14759@psf.upfronthosting.co.za>
In-reply-to
Content
With all due respect, I think that the 2.7.3 License Page is still being actively used by people as a reference, and it should be accurate. I agree that the code developers can't do anything, but the documentation for all releases, particularly in such a sensitive area as licensing, should be as up to date as possible.

Similarly, the 3.0 License page talks about a "_random" module which presumably is going ahead.  It has a license agreement displayed on the web page but I did not see that text copied into the regular LICENSE.txt that is part of the Python3 distribution, and that I assume meets the "supporting documentation" clause that all the module licenses seem to demand.

Ditto socket.
Ditto asyncore and asynchat.
Ditto Cookie.
Ditto trace.
Ditto xmlrpclib.
etcetera.

I agree this is all a documentation exercise - perhaps there is another bug tracker I should be reporting it in?
History
Date User Action Args
2012-05-09 02:06:21Jeff.Laingsetrecipients: + Jeff.Laing, r.david.murray, docs@python
2012-05-09 02:06:21Jeff.Laingsetmessageid: <1336529181.09.0.842581998436.issue14759@psf.upfronthosting.co.za>
2012-05-09 02:06:20Jeff.Lainglinkissue14759 messages
2012-05-09 02:06:20Jeff.Laingcreate