You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the code uses PY_35 flag to define async generators (__aiter__ and __anext__ methods). However, __aiter__ will be changed to a plain method instead of coroutine in the future Python versions starting from Python 3.5.2 (http://bugs.python.org/issue27243).
Though it will follow the standard deprecation process and the code would not break immediately with deprecation warnings, I think we should be aware of this issue.
Expected/Actual behaviour
In all places that define __aiter__ method, it should check also not only if the current version >= 3.5.0 but also 3.5.2.
ifPY_350orPY_351: # may need to be cleaned up@asyncio.coroutinedef__aiter___(self):
returnself@asyncio.coroutinedef__anext__(self):
...
elifPY_352:
def__aiter___(self):
returnself@asyncio.coroutinedef__anext__(self):
...
Your environment
Python 3.5.2 on MacOS X.
The text was updated successfully, but these errors were encountered:
Long story short
Currently the code uses
PY_35
flag to define async generators (__aiter__
and__anext__
methods). However,__aiter__
will be changed to a plain method instead of coroutine in the future Python versions starting from Python 3.5.2 (http://bugs.python.org/issue27243).Though it will follow the standard deprecation process and the code would not break immediately with deprecation warnings, I think we should be aware of this issue.
Expected/Actual behaviour
In all places that define
__aiter__
method, it should check also not only if the current version >= 3.5.0 but also 3.5.2.should become:
Your environment
Python 3.5.2 on MacOS X.
The text was updated successfully, but these errors were encountered: