Issue 4259: Update pydoc URLs (original) (raw)

Issue4259

➜

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/48509

classification

process

Created on 2008-11-04 21:34 by akuchling, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg75509 - (view)	Author: A.M. Kuchling (akuchling) *	Date: 2008-11-04 21:34
The URL for module documentation generated by pydoc is no longer valid. The attached patch corrects it for Python 2.5.3 by assembling the URL using the Python version. This patch shouldn't be forward-ported to 2.6 or 2.7; Sphinx changes the URL pattern further, and 2.6 and 2.7 take this into account and get their URLs correct.
msg77498 - (view)	Author: Martin v. Löwis (loewis) *	Date: 2008-12-10 08:35
The patch is fine; please apply.
msg77584 - (view)	Author: A.M. Kuchling (akuchling) *	Date: 2008-12-11 02:11
Committed to 2.5 in rev. 67693. Do I need to 'svnmerge block' this revision to prevent future merges from attempting to apply it to trunk?
msg77592 - (view)	Author: Martin v. Löwis (loewis) *	Date: 2008-12-11 06:38
> Committed to 2.5 in rev. 67693. > > Do I need to 'svnmerge block' this revision to prevent > future merges from attempting to apply it to trunk? I don't fully understand the question (did you wonder whether to invoke the block on the trunk, or on the branch?). I think this answer is "no": we neither merge from the trunk to the 2.5 branch, nor vice versa, using svnmerge.