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 terry.reedy
Recipients barry, brett.cannon, chris.jerdonek, docs@python, eric.araujo, ezio.melotti, goodger, loewis, ncoghlan, terry.reedy
Date 2014-04-25.04:16:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398399416.69.0.492010423581.issue16574@psf.upfronthosting.co.za>
In-reply-to
Content
With respect to editing final peps, I think this issue should be closed. The current PEP 1 statement accurately describes what we do, which is that in general we do not edit final peps. Moreover, Chris has not submitted a patch and I doubt anyone else knows what he thought he might add or where,

The only related question I have is in relation to Martin's point 3.
https://docs.python.org/devguide/documenting.html#id3
has the following:

pep
    A reference to a Python Enhancement Proposal. This generates appropriate index entries. The text “PEP number” is generated; in the HTML output, this text is a hyperlink to an online copy of the specified PEP.

Should we add something like "Such links should not be a substitute for properly documenting the language in the manuals."
History
Date User Action Args
2014-04-25 04:16:56terry.reedysetrecipients: + terry.reedy, loewis, barry, brett.cannon, goodger, ncoghlan, ezio.melotti, eric.araujo, chris.jerdonek, docs@python
2014-04-25 04:16:56terry.reedysetmessageid: <1398399416.69.0.492010423581.issue16574@psf.upfronthosting.co.za>
2014-04-25 04:16:56terry.reedylinkissue16574 messages
2014-04-25 04:16:56terry.reedycreate