Terry J. Reedy <tjre...@udel.edu> added the comment:
The docs pages interpret x.y as x.y.latest. So the 3.0 doc is for the 3.0.1 release, the last for 3.0. https://docs.python.org/release/3.0.1/license.html https://docs.python.org/release/3.0/license.html is fine. What's messed up is the license history table at the top due to a merge conflict artifact that should have been deleted. I am not sure whether there are also '\n's missing. The actual 3.0(.0 now) page, All 3.x branches no longer getting security fixes have been 'locked' (I am not sure of the term.) This just happened with 3.5, so 3.6. Ditto for 2.x before 2.7. (2.7 is not locked either because Benjamin has just done it yet or because he want to let people extract it. Fixing this would require one of the python/cpython owners to temporarily unlock the branch. I am closing this because I doubt any would think this important enough, but anyone is welcome to post on pydev list asking. The real problem, which we would like to fix but cannot, is web searches returning obsolete links. ---------- nosy: +terry.reedy resolution: -> out of date stage: -> resolved status: open -> closed title: The license page for Python 3.0 is messed up -> The license page for Python 3.0.1 is messed up _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42162> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
