(original) (raw)
I'm ready to accept this PEP. Because I haven't read this entire thread (and 60 messages about random diversions is really too much to try and catch up on) I'll give people 24 hours to remind me of outstanding rejections.
I also haven't reviewed the code in any detail, but I believe the code review is going well, so I'm not concerned that the PEP would have to revised based on that alone.On Fri, Sep 13, 2013 at 5:59 PM, Steven D'Aprano <steve@pearwood.info> wrote:
On Sun, Sep 08, 2013 at 10:51:57AM -0700, Guido van Rossum wrote:I've updated the PEP as requested. Is there anything further that needs
\> Never mind, I found the patch and the issue. I really think that the
\> \*PEP\* is ready for inclusion after the open issues are changed into
\> something like Discussion or Future Work, and after adding a more
\> prominent link to the issue with the patch. Then the \*patch\* can be
\> reviewed some more until it is ready -- it looks very close already.
to be done to have it approved?
http://www.python.org/dev/peps/pep-0450/
\--
Steven
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
--
--Guido van Rossum (python.org/\~guido)