[Python-Dev] Reminder: PEP 479's future about to become the default behavior (original) (raw)
Guido van Rossum guido at python.org
Tue Nov 7 21:27:53 EST 2017
- Previous message (by thread): [Python-Dev] Reminder: PEP 479's __future__ about to become the default behavior
- Next message (by thread): [Python-Dev] Clarifying Cygwin support in CPython
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks for the reminder! I don't know if it's that simple -- did you grep for occurrences of that flag (CO_FUTURE_GENERATOR_STOP)? And I suppose there are tests for both sides that need to be adjusted?
On Tue, Nov 7, 2017 at 5:17 PM, Lukasz Langa <lukasz at langa.pl> wrote:
This is according to https://www.python.org/dev/ peps/pep-0479/#transition-plan but looking at Objects/genobject.c that hasn't been implemented yet. Is this as simple as removing the
elseclause here?https://github.com/python/cpython/blob/master/Objects/ genobject.c#L277-L298 - Ł
-- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171107/3f3c9d73/attachment.html>
- Previous message (by thread): [Python-Dev] Reminder: PEP 479's __future__ about to become the default behavior
- Next message (by thread): [Python-Dev] Clarifying Cygwin support in CPython
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]