Message245727
| Author |
martin.panter |
| Recipients |
gvanrossum, martin.panter, vstinner, yselivanov |
| Date |
2015年06月24日.08:35:27 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1435134928.01.0.885019628037.issue24495@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年06月24日 08:35:28 | martin.panter | set | recipients:
+ martin.panter, gvanrossum, vstinner, yselivanov |
| 2015年06月24日 08:35:28 | martin.panter | set | messageid: <1435134928.01.0.885019628037.issue24495@psf.upfronthosting.co.za> |
| 2015年06月24日 08:35:27 | martin.panter | link | issue24495 messages |
| 2015年06月24日 08:35:27 | martin.panter | create |
|