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 steven.daprano
Recipients Mariatta, docs@python, matrixise, mdk, steven.daprano
Date 2018-12-07.06:53:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544165601.22.0.788709270274.issue35435@psf.upfronthosting.co.za>
In-reply-to
Content
Documentation is available for all versions going back to Python 1.4.

https://docs.python.org/release/1.4/

As it should be: I'm surely not the only person who has need to check old versions of the documentation from time to time. Not everyone is using the latest version of Python, and some times we need to write code that supports old versions. Leaving the old docs available is not merely "doesn't hurt", but is positively a GOOD thing to do.

We shouldn't remove the docs from the server, and we shouldn't break existing URLs.

I don't think there's much we can do about search engines: they have their secret algorithms for ranking pages, and whatever comes up is what comes up, and I doubt we can control that.

I expect that the only thing we could do is put a prominent note at the top of each page "This is an unsupported version of the docs, for the latest version see blah blah blah" and link to the most recent version.
History
Date User Action Args
2018-12-07 06:53:21steven.dapranosetrecipients: + steven.daprano, docs@python, matrixise, mdk, Mariatta
2018-12-07 06:53:21steven.dapranosetmessageid: <1544165601.22.0.788709270274.issue35435@psf.upfronthosting.co.za>
2018-12-07 06:53:21steven.dapranolinkissue35435 messages
2018-12-07 06:53:20steven.dapranocreate