[Python-Dev] Copyediting PEPs

Nick Coghlan ncoghlan at gmail.com
Wed Aug 29 06:36:44 CEST 2012


On Wed, Aug 29, 2012 at 2:03 PM, Chris Angelico <rosuav at gmail.com> wrote:
> What's the procedure for making trivial edits to a PEP? I was
> (re)reading PEP 393 and found a couple of typos (PyCompactObject s/be
> PyCompactUnicodeObject and "differs form length" s/be "from"). Can I
> edit them directly in the web site's SVN repo, or should a patch be
> submitted?
>
> Apologies for the perhaps clueless question!

Sending a patch to the PEP editors (peps at python.org) or posting it to
the tracker is likely the best option. However, in the general case,
we don't worry too much about minor errors in accepted and final PEPs
- once the PEP is implemented, they're mostly historical records
rather than reference documents (some exceptions do exist, but those
mostly related to items that weren't properly documented in the
language and library reference. The two most notable offenders, PEP
302 and 3118, have finally been replaced by more comprehensive
documentation for the import system and binary buffer protocol in the
official docs for 3.3)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia


More information about the Python-Dev mailing list