This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Ilya.Kulakov
Recipients Ilya.Kulakov, gvanrossum, r.david.murray, vstinner, yselivanov
Date 2016-05-10.19:10:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yury, we're building our own CPython anyway (and we just updated to 3.5.1). I'd be glad to test the patch during the next iteration.

Guido, I think my use case mixes up other things I find confusing about asyncio: e.g. inablitity to synchronously perform code written as standalone coroutine. It deserves its own task and discussion.

The purpose of this request is that access to a running loop is handy within coroutine. It's already there, since coroutine is executed within its context. However, instead of "self" library provides API to only access some globally default loop.

Python does not require a user to pass self whenever instance methods needs to be called. I consider relationship between event loop and awaitables alike.
Date User Action Args
2016-05-10 19:10:53Ilya.Kulakovsetrecipients: + Ilya.Kulakov, gvanrossum, vstinner, r.david.murray, yselivanov
2016-05-10 19:10:52Ilya.Kulakovsetmessageid: <>
2016-05-10 19:10:52Ilya.Kulakovlinkissue26969 messages
2016-05-10 19:10:52Ilya.Kulakovcreate