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 brandon-rhodes
Recipients brandon-rhodes, docs@python
Date 2013-03-07.01:13:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362618784.61.0.181108502719.issue17370@psf.upfronthosting.co.za>
In-reply-to
Content
A friend (@theomn on Twitter) was just working off of PEP-333 when I mentioned to him that PEP-3333, and he had never heard of it, and he expressed the wish that PEPs would have a banner or something at the top if there is a more recent version of them. I think his idea is great, and is like the feature of PyPI where if Google lands you on an old version of a package then it is careful to tell you up at the top that a more recent version is available.

This could extend to all sorts of cross-references that we should maintain: some PEPs have been superseded; others have more recent supplements that people should read as well (think of the relationship between packaging PEPs); PEPs that did not wind up being implemented have cousins who were; and so forth.

Is this something that needs to wait until the New Python Web Site appears, and that would be meta-markup somehow maintained along with the PEP texts themselves? Or should there be a “Related PEPs” paragraph that we open at the top of each relevant PEP and just include the cross-links as raw updates to the PEP's own restructured text? I'm open to a simple implementation here, so long as we can provide more “community context” when people land on a PEP.
History
Date User Action Args
2013-03-07 01:13:04brandon-rhodessetrecipients: + brandon-rhodes, docs@python
2013-03-07 01:13:04brandon-rhodessetmessageid: <1362618784.61.0.181108502719.issue17370@psf.upfronthosting.co.za>
2013-03-07 01:13:04brandon-rhodeslinkissue17370 messages
2013-03-07 01:13:04brandon-rhodescreate