Message183625
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. |
|
Date |
User |
Action |
Args |
2013-03-07 01:13:04 | brandon-rhodes | set | recipients:
+ brandon-rhodes, docs@python |
2013-03-07 01:13:04 | brandon-rhodes | set | messageid: <1362618784.61.0.181108502719.issue17370@psf.upfronthosting.co.za> |
2013-03-07 01:13:04 | brandon-rhodes | link | issue17370 messages |
2013-03-07 01:13:04 | brandon-rhodes | create | |
|