With the conversion to mercurial source links in documentation should now point to hg.python.org
Here is the patch.

Good point. However, making the change won't help the already generated versions of the 3.2 html doc, like those included with installers or any older URL references elsewhere to the svn source.  Perhaps some URL rewrite rules should be added to the web server to redirect "source code" URLs from svn.python.org to hg.python.org style?

IIUC those svn links will keep working for some time, but if/when the svn repo and/or viewvc will be removed an URL rewrite rule should be fix the problem.
The patch seems OK to me.

I've put the redirection in place.

Antoine, great!  How about also for the other "active" branches now in hg:
release{32,31,27,26,25-maint} ?

> Antoine, great!  How about also for the other "active" branches now in hg:
> release{32,31,27,26,25-maint} ?

Is there any such reference in the docs?

Right: no comprehensive links like in the 3.2+ versions. I just see a few miscellaneous links elsewhere in the source. But there are undoubtedly plenty of links elsewhere out in the wild.  So this is probably out-of-scope for this issue but should be dealt with elsewhere as part of a long-term migration plan for svn.python.org.  I'll bring it up on python-dev.

> I've put the redirection in place.
So, it's not possible to access http://svn.python.org/view/python/branches/py3k/ at all now?

> So, it's not possible to access http://svn.python.org/view/python
> /branches/py3k/ at all now?

Hmm, apparently no. Is it important?

The svn repos and viewvc won't disappear soon because they are used for other things (e.g. the tracker).  I think it's better to avoid redirects until svn and/or viewvc are definitely gone.

> The svn repos and viewvc won't disappear soon because they are used
> for other things (e.g. the tracker).  I think it's better to avoid
> redirects until svn and/or viewvc are definitely gone.

The redirect is only for the py3k branch, something nobody should use
anymore.

This can be closed.

This issue is not about the redirects. It is about links in documentation. The redirect is great for the links in the wild, the online documentation, however, could and should use proper links without any redirects.

Georg, or whoever is maintainer of Doc/tools/sphinxext/pyspecific.py, could you please have a look at the patch.

New changeset 3c1e779002d3 by Ezio Melotti in branch '3.2':
#11435: Update the links generated by the source directive to use hg.python.org.
http://hg.python.org/cpython/rev/3c1e779002d3

New changeset 5f220e98eddc by Ezio Melotti in branch 'default':
#11435: Merge with 3.2
http://hg.python.org/cpython/rev/5f220e98eddc

Now it's fixed in 3.2 and 3.3.  Thanks for the patch!

The 2.7 docs link to the Subversion repo.  Can I update them?

Patch to fix links in the 3.2 docs.

New changeset 79d2682c4fc5 by Ezio Melotti in branch '3.2':
#11435: link to the correct branch.
http://hg.python.org/cpython/rev/79d2682c4fc5

New changeset 3028b5ab92c0 by Ezio Melotti in branch 'default':
#11435: dummy merge with 3.2.
http://hg.python.org/cpython/rev/3028b5ab92c0

I fixed the URL in 3.2.

> The 2.7 docs link to the Subversion repo.  Can I update them?

2.7 doesn't have the source directive, do you want to replace all the svn links manually?
If so, either reopen this issue or create a new one.

Thanks for the commit, I intended to do it these days.

For 2.7, I was indeed talking about updated all manual links.  sed is my friend :)

Georg or Benjamin: The PEP/documents/scripts used for releases should also mention/edit the version in Doc/tools/sphinxext/pyspecific.py.

Done (in rev e32f140a020b).

After getting Georg’s greenlight on python-dev, I have adapted the source reST role for 2.7 and updated all links.