Fwd: Old link text in documentation
Could (and should) the online Python 3.1 docs be updated to show Python 2.7 as stable? All the best, Michael -------- Original Message -------- Subject: Old link text in documentation Date: Sun, 15 Aug 2010 15:49:34 -0700 From: Aaron DeVore <aaron.devore@gmail.com> To: webmaster@python.org The link text at http://docs.python.org/py3k/ under "Docs for other versions" still describes 2.7 as being "in development" -Aaron DeVore
Am 18.08.2010 17:11, schrieb Michael Foord:
Could (and should) the online Python 3.1 docs be updated to show Python 2.7 as stable?
I think the answer is "no, it could not". How many old documentation sets would you want to go through, and regenerate them? There is also http://docs.python.org/release/2.6.5/ http://docs.python.org/release/2.6.4/ http://docs.python.org/release/2.6.3/ etc. In particular, http://docs.python.org/release/2.6.2/ still lists 3.1 as in-development. If that would be fixed, I think the fix should work for all documentation sets, and such a fix might be difficult to implement. Regards, Martin
On 18/08/2010 21:59, "Martin v. Löwis" wrote:
Am 18.08.2010 17:11, schrieb Michael Foord:
Could (and should) the online Python 3.1 docs be updated to show Python 2.7 as stable?
I think the answer is "no, it could not".
How many old documentation sets would you want to go through, and regenerate them? There is also
http://docs.python.org/release/2.6.5/ http://docs.python.org/release/2.6.4/ http://docs.python.org/release/2.6.3/
etc.
In particular,
http://docs.python.org/release/2.6.2/
still lists 3.1 as in-development.
If that would be fixed, I think the fix should work for all documentation sets, and such a fix might be difficult to implement.
Ok, fair enough. Michael
Regards, Martin
Am 18.08.2010 20:59, schrieb "Martin v. Löwis":
Am 18.08.2010 17:11, schrieb Michael Foord:
Could (and should) the online Python 3.1 docs be updated to show Python 2.7 as stable?
I think the answer is "no, it could not".
How many old documentation sets would you want to go through, and regenerate them? There is also
http://docs.python.org/release/2.6.5/ http://docs.python.org/release/2.6.4/ http://docs.python.org/release/2.6.3/
etc.
In particular,
http://docs.python.org/release/2.6.2/
still lists 3.1 as in-development.
If that would be fixed, I think the fix should work for all documentation sets, and such a fix might be difficult to implement.
Actually, the ones referred to here are the continually updated docs from the branch head, which I just fixed to show the correct information. I agree about the doc sets specific to releases. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.
participants (3)
-
"Martin v. Löwis" -
Georg Brandl -
Michael Foord