Message343092
| Author | alex.gronholm |
|---|---|
| Recipients | alex.gronholm, asvetlov, yselivanov |
| Date | 2019-05-21.20:45:37 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1558471537.52.0.812163346713.issue36999@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
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 libraries I need this object, sometimes for debugging and other times for implementing "crazy" schemes like running parts of the the coroutine function code in a worker thread. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-05-21 20:45:37 | alex.gronholm | set | recipients: + alex.gronholm, asvetlov, yselivanov |
| 2019-05-21 20:45:37 | alex.gronholm | set | messageid: <1558471537.52.0.812163346713.issue36999@roundup.psfhosted.org> |
| 2019-05-21 20:45:37 | alex.gronholm | link | issue36999 messages |
| 2019-05-21 20:45:37 | alex.gronholm | create | |