[issue16746] clarify what should be sent to peps@

Chris Jerdonek added the comment: By the way, thanks for the clarifying info, David. Also, I thought I was the one that was going to be accused of reading the original text like a computer. :) -- ___ Python tracker

[issue16746] clarify what should be sent to peps@

Chris Jerdonek added the comment: This issue was just addressed by Nick's fix for issue 16581, specifically the following parts of http://hg.python.org/peps/rev/24d5623ab21e : + is a mailing list consisting of PEP editors. All +email related to PEP administration (such as requesting a PEP numb

[issue16746] clarify what should be sent to peps@

R. David Murray added the comment: The editors do more than your sentence suggests. They also (sometimes) edit peps, (sometimes) provide advice about preparing one, and commit and update peps when the author(s) do not have commit access. The distinction in the types of email that PEP 1 is att

[issue16746] clarify what should be sent to peps@

Changes by Brett Cannon : -- assignee: -> brett.cannon nosy: +brett.cannon priority: normal -> low stage: -> patch review ___ Python tracker ___ ___

[issue16746] clarify what should be sent to peps@

Changes by Chris Jerdonek : -- keywords: +patch Added file: http://bugs.python.org/file28389/issue-16746-1.patch ___ Python tracker ___ __

[issue16746] clarify what should be sent to peps@

New submission from Chris Jerdonek: Currently, PEP 1 can be read to mean that should be CC'ed on all e-mails related to PEPs. However, this isn't the intent because, for example, it is okay to have discussions about PEPs on python-dev or python-ideas without involving . I'm attaching a patc