[docs] [issue16574] clarify policy on updates to final peps
report at bugs.python.org
Thu Nov 29 04:45:47 CET 2012
Éric Araujo added the comment:
I think the gist here is that “in general” is good enough, given that there is unwritten consensus about what edits are possible in the developers’ heads. Most of the time unwritten knowledge is not good, but (if I get what Martin and Barry mean correctly) for PEP rules this is fine. We don’t want an over-detailed or inflexible process.
About the mail from Nick: it was talking about writing a new informational PEP, so I don’t see the link with final standards track PEPs.
Python tracker <report at bugs.python.org>
More information about the docs