delta/cpython-git.git/Lib/asyncio/tasks.py, branch enum-private-310

bpo-39529: Deprecate creating new event loop in asyncio.get_event_loop() (GH-23554)

2021-04-25T10:40:44+00:00

asyncio.get_event_loop() emits now a deprecation warning when it creates a new event loop.
In future releases it will became an alias of asyncio.get_running_loop().

bpo-41891: ensure asyncio.wait_for waits for task completion (#22461)

2020-12-18T17:26:04+00:00

bpo-42582: Remove asyncio._all_tasks_compat(). (GH-23664)

2020-12-06T16:54:33+00:00

It was used to implement now removed asyncio.Task.all_tasks().

bpo-42392: Remove loop parameter from asyncio.tasks and asyncio.subprocess (GH-23521)

2020-11-28T08:21:17+00:00

bpo-42392: Remove loop parameter form asyncio locks and Queue (#23420)

2020-11-24T18:08:54+00:00

Co-authored-by: Andrew Svetlov

bpo-42140: Improve asyncio.wait function (GH-22938)

2020-11-10T22:12:52+00:00

# Improve asyncio.wait function

The original code creates the futures set two times.
We can create this set before, avoiding the second creation.

This new behaviour [breaks the aiokafka library](https://github.com/aio-libs/aiokafka/pull/672), because it gives an iterator to that function, so the second iteration become empty.

Automerge-Triggered-By: GH:1st1

bpo-42230: Improve asyncio documentation regarding accepting sets vs iterables (GH-23073)

2020-11-02T10:56:35+00:00

People call wait() and as_completed() with various non-set iterables,
a list should be the most common but there are others as well[1].

Considering typeshed also documents wait()[2] and as_completed()[3]
as accepting arbitrary iterables I think it's a good idea to document
the status quo better.

[1] https://github.com/aio-libs/aiokafka/pull/672
[2] https://github.com/python/typeshed/blob/620989bac572f30349b95590ebe81a73ce0fe862/stdlib/3/asyncio/tasks.pyi#L161
[3] https://github.com/python/typeshed/blob/620989bac572f30349b95590ebe81a73ce0fe862/stdlib/3/asyncio/tasks.pyi#L40

bpo-37658: Fix asyncio.wait_for() to respect waited task status (#21894)

2020-08-26T16:42:45+00:00

Currently, if `asyncio.wait_for()` itself is cancelled it will always
raise `CancelledError` regardless if the underlying task is still
running.  This is similar to a race with the timeout, which is handled
already.

bpo-32751: Wait for task cancel in asyncio.wait_for() when timeout <= 0 (#21895)

2020-08-26T16:42:22+00:00

When I was fixing bpo-32751 back in GH-7216 I missed the case when
*timeout* is zero or negative.  This takes care of that.

Props to @aaliddell for noticing the inconsistency.

bpo-37703: improve asyncio.gather documentation regarding cancellation (GH-15312)

2020-07-20T08:42:57+00:00

These changes updates the doc to comprehensively mention the behaviour of gather.cancel()

Automerge-Triggered-By: @asvetlov