Skip to content

Commit eadc0fb

Browse files
committed
consistent spacing
1 parent 1abe9a1 commit eadc0fb

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

Doc/howto/a-conceptual-overview-of-asyncio.rst

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,6 @@ A conceptual overview part 1: the high-level
3131
In part 1, we'll cover the main, high-level building blocks of asyncio: the
3232
event loop, coroutine functions, coroutine objects, tasks and ``await``.
3333

34-
3534
==========
3635
Event Loop
3736
==========
@@ -149,8 +148,6 @@ For example::
149148
Hello
150149
7
151150

152-
153-
154151
=====
155152
Tasks
156153
=====
@@ -243,7 +240,6 @@ The event loop then works through its queue, calling ``coro_b()`` and then
243240
I am coro_a(). Hi!
244241
I am coro_a(). Hi!
245242
246-
247243
------------------------------------------------
248244
A conceptual overview part 2: the nuts and bolts
249245
------------------------------------------------
@@ -363,7 +359,6 @@ Futures are much more versatile and will be marked as done when you say so.
363359
In this way, they're the flexible interface for you to make your own conditions
364360
for waiting and resuming.
365361

366-
367362
========================
368363
A homemade asyncio.sleep
369364
========================
@@ -420,7 +415,6 @@ will monitor how much time has elapsed and accordingly call
420415
# Block until the future is marked as done.
421416
await future
422417

423-
424418
We'll use a rather bare object ``YieldToEventLoop()`` to ``yield`` from its
425419
``__await__`` in order to cede control to the event loop.
426420
This is effectively the same as calling ``asyncio.sleep(0)``, but this approach

0 commit comments

Comments
 (0)