New submission from Martin Panter:

While trying to port the example at 
<https://docs.python.org/3.5/library/asyncio-task.html#example-future-with-run-until-complete>
 to use “async def”, I discovered the ensure_future() function does not like 
the coroutine field name changes introduced in Issue 24400:

>>> asyncio.ensure_future(slow_operation(future))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/proj/python/cpython/Lib/asyncio/futures.py", line 196, in __repr__
    info = self._repr_info()
  File "/home/proj/python/cpython/Lib/asyncio/tasks.py", line 105, in _repr_info
    coro = coroutines._format_coroutine(self._coro)
  File "/home/proj/python/cpython/Lib/asyncio/coroutines.py", line 242, in 
_format_coroutine
    filename = coro.gi_code.co_filename
AttributeError: 'coroutine' object has no attribute 'gi_code'

I understand the gi_ names all changed to cr_, so I guess this code has to 
adjust as well.

----------
components: asyncio
messages: 245727
nosy: gvanrossum, haypo, vadmium, yselivanov
priority: normal
severity: normal
stage: needs patch
status: open
title: asyncio.ensure_future() AttributeError with “async def” coroutines
type: behavior
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue24495>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to