Since the AsynchronousTask.wait() method is prone to event loop
recursion, deprecate it, and add an async_wait() method method to
replace it. Instead of using task.wait() in order to implicitly run
the event loop, now loop.run_until_complete(task.async_wait()) will
be used to explicitly run the
Add an AsynchronousTask.scheduler attribute, which will hold an event
loop instance in order to work with Future instances. Name the
attribute "scheduler" because this is the name used by many existing
subclasses of AsynchronousTask. Since the AsyncScheduler class already
has an _event_loop
Since the AsynchronousTask.wait() method is prone to event loop
recursion, deprecate it, and add an async_wait() method method to
replace it. Instead of using task.wait() in order to implicitly run
the event loop, now loop.run_until_complete(task.async_wait()) will
be used to explicitly run the
On 04/23/2018 09:10 AM, Brian Dolbec wrote:
> On Sun, 22 Apr 2018 15:30:09 -0700
> Zac Medico wrote:
>
>> Bug: https://bugs.gentoo.org/653810
>>
>> Zac Medico (5):
>> portdbapi: add async_fetch_map method (bug 653810)
>> EbuildFetcher: inherit CompositeTask (bug 653810)
On Sun, 22 Apr 2018 15:30:09 -0700
Zac Medico wrote:
> Bug: https://bugs.gentoo.org/653810
>
> Zac Medico (5):
> portdbapi: add async_fetch_map method (bug 653810)
> EbuildFetcher: inherit CompositeTask (bug 653810)
> EbuildFetcher: add _async_uri_map method (bug