[issue35435] Documentation of 3.3 is available

[Ned Deily]

Ned Deily  added the comment:

> I think as it stands, this ticket is "not a bug".

Indeed, this is not only not a bug, it's a feature that the docs for every 
Python release family are available on-line.  That said, we do have two sets of 
URLs that point to these docs:

1. https://docs.python.org/release/x.y.z/ which is the canonical link to the 
docs for a particular release and linked to from 
https://www.python.org/doc/versions/

2. https://docs.python.org/x.y/ (along with /x) which points to the most recent 
top of branch doc build for that branch.  For the next feature release branch 
(master) and branches still in bug-fix mode, the docs are automatically updated 
several times a day.  For 2.x and 3.x branches in security-fix mode or at 
end-of-life (retired), there are symlinks here that point to the doc set for 
the most recent release of that branch, i.e. the same doc set available in 
https://docs.python.org/release/x.y.z/.

There is already in place a restriction in the robots.txt file for the 
docs.python.org server to not webcrawl anything under /release but there is 
nothing (AFAICT) telling webcrawlers to ignore the "symlinked" aliases at /x.y, 
and that would seem to be the case here.

Without spending too much time on it, it seems to me there are s number of 
issues here:
1. What URL schemes do we have and want to continue to support?
2. What things do we want to show up in search engine results?
3. How do we make that happen?
4. How do we maintain this going forward?

One possibility that comes to mind:
1. unchanged from today
2. just the most current 3.x maintenance release (e.g. today 3.7)?  People 
needing accessing to other current or security-fix branches (dev, 3.6, 2.7, 
3.5) can access those docsets through the version switcher pulldown on the doc 
webpages.
3. What isn't so obvious today is how to get to docsets for other, older 
releases.  For that, perhaps we could add an "Other ..." or some such item to 
the version switcher list that would link to the complete list at 
https://www.python.org/doc/versions/ ?
4. If we think it is important to indefinitely provide the links at 
https://docs.python.org/x.y/ even after the release is retired, we could add a 
step to the release process to add an entry to robots.txt when a release enters 
security-fix-mode ?  Or earlier?  That gets back to question 2.

I think this all is something for our release docs expert, Julien, to look into.

--
assignee: docs@python -> mdk
nosy: +ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35435] Documentation of 3.3 is available

[Mariatta Wijaya]

Mariatta Wijaya  added the comment:

> 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.


Not sure how straightforward it will be to do this, and whether it will worth 
the trouble. Julien, perhaps you know more about this and can provide 
assessment. Perhaps it needs to be done from within python-docs-theme?

FWIW, the landing page of each version (example https://docs.python.org/3.3/) 
states when it was last built. It can be an indication that it is outdated.

There's also a related issue in python.org to better inform people of which 
Python versions are still maintained or not: 
https://github.com/python/pythondotorg/issues/1302

I think as it stands, this ticket is "not a bug".

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35435] Documentation of 3.3 is available

[Julien Palard]

Julien Palard  added the comment:

> 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.

I'm +1 on this, and it can even help search engine algorithms to rank the right 
pages (as receiving more links than the old page).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35435] Documentation of 3.3 is available

[Steven D'Aprano]

Steven D'Aprano  added the comment:

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.

--
nosy: +steven.daprano

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35435] Documentation of 3.3 is available

[Mariatta Wijaya]

Mariatta Wijaya  added the comment:

It seems like all other versions (3.2, 3.1, 3.0) are still available too, just 
not updated anymore.

I'm thinking it's ok to leave these documentation.
While we don't support these versions anymore,  they still exists, and they're 
even still available for download from python.org/downloads. It doesn't hurt to 
keep these docs.

--
nosy: +Mariatta

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35435] Documentation of 3.3 is available

[Stéphane Wirtel]

New submission from Stéphane Wirtel :

Today, I was looking for the doc of unittest.mock and the result from 
DuckDuckGo was this link: 
https://docs.python.org/3.3/library/unittest.mock-examples.html

In the devguide, we stopped the support and everything about this version, in 
the bug tracker, 3.3 is not available.

Maybe we could remove the doc from the server.

--
assignee: docs@python
components: Documentation
messages: 331271
nosy: docs@python, matrixise, mdk
priority: normal
severity: normal
status: open
title: Documentation of 3.3 is available

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com