1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
Using asyncio
=============
.. currentmodule:: websockets
How do I run two coroutines in parallel?
----------------------------------------
You must start two tasks, which the event loop will run concurrently. You can
achieve this with :func:`asyncio.gather` or :func:`asyncio.create_task`.
Keep track of the tasks and make sure they terminate or you cancel them when
the connection terminates.
Why does my program never receive any messages?
-----------------------------------------------
Your program runs a coroutine that never yields control to the event loop. The
coroutine that receives messages never gets a chance to run.
Putting an ``await`` statement in a ``for`` or a ``while`` loop isn't enough
to yield control. Awaiting a coroutine may yield control, but there's no
guarantee that it will.
For example, :meth:`~legacy.protocol.WebSocketCommonProtocol.send` only yields
control when send buffers are full, which never happens in most practical
cases.
If you run a loop that contains only synchronous operations and
a :meth:`~legacy.protocol.WebSocketCommonProtocol.send` call, you must yield
control explicitly with :func:`asyncio.sleep`::
async def producer(websocket):
message = generate_next_message()
await websocket.send(message)
await asyncio.sleep(0) # yield control to the event loop
:func:`asyncio.sleep` always suspends the current task, allowing other tasks
to run. This behavior is documented precisely because it isn't expected from
every coroutine.
See `issue 867`_.
.. _issue 867: https://github.com/python-websockets/websockets/issues/867
Why am I having problems with threads?
--------------------------------------
If you choose websockets' default implementation based on :mod:`asyncio`, then
you shouldn't use threads. Indeed, choosing :mod:`asyncio` to handle concurrency
is mutually exclusive with :mod:`threading`.
If you believe that you need to run websockets in a thread and some logic in
another thread, you should run that logic in a :class:`~asyncio.Task` instead.
If it blocks the event loop, :meth:`~asyncio.loop.run_in_executor` will help.
This question is really about :mod:`asyncio`. Please review the advice about
:ref:`asyncio-multithreading` in the Python documentation.
Why does my simple program misbehave mysteriously?
--------------------------------------------------
You are using :func:`time.sleep` instead of :func:`asyncio.sleep`, which
blocks the event loop and prevents asyncio from operating normally.
This may lead to messages getting send but not received, to connection
timeouts, and to unexpected results of shotgun debugging e.g. adding an
unnecessary call to :meth:`~legacy.protocol.WebSocketCommonProtocol.send`
makes the program functional.
|
