Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update pydoc URLs #48509

Closed
akuchling opened this issue Nov 4, 2008 · 4 comments
Closed

Update pydoc URLs #48509

akuchling opened this issue Nov 4, 2008 · 4 comments
Assignees
@akuchling
Labels
release-blocker

Comments

@akuchling
Copy link
Member

BPO 4259
Nosy @loewis, @akuchling
Files
  • pydoc-patch.txt: Patch for pydoc URLs
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = 'https://github.com/akuchling'
closed_at = <Date 2008-12-11.02:11:34.189>
created_at = <Date 2008-11-04.21:34:07.148>
labels = ['release-blocker']
title = 'Update pydoc URLs'
updated_at = <Date 2008-12-11.06:38:41.979>
user = 'https://github.com/akuchling'

    bugs.python.org fields:

    activity = <Date 2008-12-11.06:38:41.979>
actor = 'loewis'
assignee = 'akuchling'
closed = True
closed_date = <Date 2008-12-11.02:11:34.189>
closer = 'akuchling'
components = []
creation = <Date 2008-11-04.21:34:07.148>
creator = 'akuchling'
dependencies = []
files = ['11943']
hgrepos = []
issue_num = 4259
keywords = []
message_count = 4.0
messages = ['75509', '77498', '77584', '77592']
nosy_count = 2.0
nosy_names = ['loewis', 'akuchling']
pr_nums = []
priority = 'release blocker'
resolution = 'accepted'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue4259'
versions = ['Python 2.5.3']
    @akuchling
    Copy link
    Member Author

    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.

    @loewis
    Copy link
    Mannequin

    loewis mannequin commented Dec 10, 2008

    The patch is fine; please apply.

    @loewis loewis mannequin added the release-blocker label Dec 10, 2008
    @loewis loewis mannequin assigned akuchling Dec 10, 2008
    @akuchling
    Copy link
    Member Author

    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?

    @loewis
    Copy link
    Mannequin

    loewis mannequin commented Dec 11, 2008

    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.

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Assignees

    @akuchling akuchling

    Labels
    release-blocker
    Projects
    None yet
    Milestone
    No milestone
    Development

    No branches or pull requests
    1 participant
    @akuchling