Nicklas Lindgren 3c4141982e Declare asyncio.as_completed() as taking an Iterable (#3164) ...

The stub for asyncio.as_completed declared it as taking a Sequence of
Futures. This was unnecessarily strict.

Just like asyncio.wait, asyncio.as_completed can be declared to take
an Iterable of Futures instead. Both these functions iterate over
their argument only once to store its items in a set, so an Iterable
is sufficiently strict. This has been true since the initial
implementation of the functions.

2019-07-31 10:53:23 -07:00

..

__init__.pyi

Remove Python 3.4 support (#3147)

2019-07-27 10:58:21 +02:00

base_events.pyi

Remove Python 3.4 support (#3147)

2019-07-27 10:58:21 +02:00

coroutines.pyi

Move asyncio from 3.4 to 3 (#2307)

2018-07-03 09:06:04 -07:00

events.pyi

Remove Python 3.4 support (#3147)

2019-07-27 10:58:21 +02:00

futures.pyi

Remove Python 3.4 support (#3147)

2019-07-27 10:58:21 +02:00

locks.pyi

Move asyncio from 3.4 to 3 (#2307)

2018-07-03 09:06:04 -07:00

protocols.pyi

bring protocols.pyi more inline with documentation (#2421)

2018-08-31 13:56:57 +02:00

queues.pyi

Remove Python 3.4 support (#3147)

2019-07-27 10:58:21 +02:00

runners.pyi

Add missing asyncio 3.7 top-level functions (#2320)

2018-07-20 08:10:52 -07:00

streams.pyi

Use variable annotations everywhere (#2909)

2019-04-13 10:40:52 +02:00

subprocess.pyi

Use variable annotations everywhere (#2909)

2019-04-13 10:40:52 +02:00

tasks.pyi

Declare asyncio.as_completed() as taking an Iterable (#3164)

2019-07-31 10:53:23 -07:00

transports.pyi

Move asyncio from 3.4 to 3 (#2307)

2018-07-03 09:06:04 -07:00