[issue22863] https://docs.python.org/ should make a true 2.7.8 version available
New submission from Marc-Andre Lemburg: The documentation shown for Python 2.7.8 currently includes 2.7.9 parts, e.g. for the ssl modules (https://docs.python.org/2.7/library/ssl.html). Since there were so many changes to the ssl module for 2.7.9 which are not available in 2.7.8, I think it would be good to be able to not only select "2.7.8" from the doc version drop-down, but to also really get that particular version of the documentation, and provide a separate "2.7.9" snapshop as well. I tried https://docs.python.org/2.7.8/library/ssl.html, but that doesn't seem to exist. PS: I'm not sure whether this is the right tracker to report this. Feel free to move it elsewhere. ---------- assignee: docs@python components: Documentation messages: 231113 nosy: docs@python, lemburg priority: normal severity: normal status: open title: https://docs.python.org/ should make a true 2.7.8 version available versions: Python 2.7 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue22863> _______________________________________
Benjamin Peterson added the comment: There's https://docs.python.org/release/2.7.8/ ---------- nosy: +benjamin.peterson _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue22863> _______________________________________
Terry J. Reedy added the comment: New stuff is marked "New in version 2.7.9.", etc. The Idle chapter (reletively new in the Library Reference itself) has the same problem if new or quasi-new features in micro-releases are added to the doc before the release. ---------- nosy: +terry.reedy _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue22863> _______________________________________
Marc-Andre Lemburg added the comment: On 14.11.2014 22:35, Terry J. Reedy wrote:
New stuff is marked "New in version 2.7.9.", etc. The Idle chapter (reletively new in the Library Reference itself) has the same problem if new or quasi-new features in micro-releases are added to the doc before the release.
I know, but there are so many additions in the ssl module that it's very difficult to tell what actually was part of earlier Python 2.7 releases. I think best would be to link to the release URL Bejamin mentioned for "2.7.8" and provide the trunk version as "2.7 (trunk)". The same should probably be done for the other releases listed in the selector. ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue22863> _______________________________________
Terry J. Reedy added the comment: I agree that "x.y.z" should be reserved for the frozen release version of the docs and that the current ongoing version should be "x.y (trunk)" or "x.y.z+". This was true without new features in a micro release, but did not matter so much. Leaving Idle aside, I am not sure how we should handle the new exception in other stdlib modules. There may or may not be more documented additions past 2.7.9. ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue22863> _______________________________________
Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA@GMail.Com>: ---------- nosy: +Arfrever _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue22863> _______________________________________
Zachary Ware <zachary.ware@gmail.com> added the comment: As 2.7 is now EOL, I'm closing this issue. ---------- nosy: +zach.ware resolution: -> out of date stage: -> resolved status: open -> closed _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue22863> _______________________________________
participants (5)
-
Arfrever Frehtes Taifersar Arahesis -
Benjamin Peterson
-
Marc-Andre Lemburg
-
Terry J. Reedy
-
Zachary Ware