[Python-Dev] Two small PEP ideas (original) (raw)
Barry Warsaw barry at python.org
Fri Apr 30 21:09:18 CEST 2010
- Previous message: [Python-Dev] Two small PEP ideas
- Next message: [Python-Dev] Two small PEP ideas
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Apr 28, 2010, at 09:22 AM, Dirkjan Ochtman wrote:
On Tue, Apr 27, 2010 at 23:55, Nick Coghlan <ncoghlan at gmail.com> wrote:
I believe the more important part of Barry's suggested change here is requiring a link to the archived message (usually from python-dev) where the PEP was accepted (be it directly by you as BDFL, or by consensus from a "sufficient" number of core developers). This will likely also help with reminding people to announce on python-dev when PEPs are accepted by consensus (or by you) somewhere like PyCon or a sprint. Though maybe it should be called Conclusion instead of Accepted and used for Rejected PEPs, as well?
Good point. What do you think about 'Resolution'?
As to Guido's point about the decision making process, Nick's right. I just want to make sure we can capture the resolution in the PEP, be it by BDFL pronouncement or "hey, silence is acceptance" email.
Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20100430/9bcc6b92/attachment.pgp>
- Previous message: [Python-Dev] Two small PEP ideas
- Next message: [Python-Dev] Two small PEP ideas
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]