[issue36999] Expose the coroutine object in asyncio task objects

Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue36999] Expose the coroutine object in asyncio task objects

miss-islington added the comment: New changeset 98ef92002ec289bf8086b0ef3d4f96c2589f4e68 by Miss Islington (bot) (Alex Grönholm) in branch 'master': bpo-36999: Add asyncio.Task.get_coro() (GH-13680) https://github.com/python/cpython/commit/98ef92002ec289bf8086b0ef3d4f96c2589f4e68 --

[issue36999] Expose the coroutine object in asyncio task objects

Change by Alex Grönholm : -- keywords: +patch pull_requests: +13568 stage: -> patch review pull_request: https://github.com/python/cpython/pull/13680 ___ Python tracker ___

[issue36999] Expose the coroutine object in asyncio task objects

Alex Grönholm added the comment: I'll look into making a PR. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36999] Expose the coroutine object in asyncio task objects

Yury Selivanov added the comment: I've no problem with this. We can add a 'get_coro()' Task method (this is in line with asyncio usually having the "getter" api as opposed to properties). -- ___ Python tracker

[issue36999] Expose the coroutine object in asyncio task objects

New submission from Alex Grönholm : Both curio and trio expose the coroutine object belonging to a task as the "coro" attribute. Asyncio exposes this as "_coro" (as does uvloop) but it would be nice to have at least a read-only attribute exposing this as part of the public API. In some of my