I have this Cython code (simplified):
class Callback:
async def foo(self):
print(\'called\')
cdef void call_foo(void* callback):
print(\'call_fo
TLDR:
Coroutines must be await
'ed or run by an event loop. A cdef
function cannot await
, but it can construct and return a coroutine.
Your actual problem is mixing synchronous with asynchronous code. Case in point:
async def example():
loop.run_until_complete(py_call_foo())
This is similar to putting a subroutine in a Thread, but never starting it. Even when started, this is a deadlock: the synchronous part would prevent the asynchronous part from running.
await
edAn async def
coroutine is similar to a def ...: yield
generator: calling it only instantiates it. You must interact with it to actually run it:
def foo():
print('running!')
yield 1
bar = foo() # no output!
print(next(bar)) # prints `running!` followed by `1`
Similarly, when you have an async def
coroutine, you must either await
it or schedule it in an event loop. Since asyncio.wait_for produces a coroutine, and you never await
or schedule it, it is not run. This is the cause of the RuntimeWarning
.
Note that the purpose of putting a coroutine into asyncio.wait_for
is purely to add a timeout. It produces an asynchronous wrapper which must be await
'ed.
async def call_foo(callback):
print('call_foo')
await asyncio.wait_for(callback.foo(), timeout=2)
asyncio.get_event_loop().run_until_complete(call_foo(Callback()))
The key for asynchronous programming is that it is cooperative: Only one coroutine executes until it yields control. Afterwards, another coroutine executes until it yields control. This means that any coroutine blocking without yielding control blocks all other coroutines as well.
In general, if something performs work without an await
context, it is blocking. Notably, loop.run_until_complete
is blocking. You have to call it from a synchronous function:
loop = asyncio.get_event_loop()
# async def function uses await
async def py_call_foo():
await call_foo(Callback())
# non-await function is not async
def example():
loop.run_until_complete(py_call_foo())
example()
A coroutine can return
results like a regular function.
async def make_result():
await asyncio.sleep(0)
return 1
If you await
it from another coroutine, you directly get the return value:
async def print_result():
result = await make_result()
print(result) # prints 1
asyncio.get_event_loop().run_until_complete(print_result())
To get the value from a coroutine inside a regular subroutine, use run_until_complete
to run the coroutine:
def print_result():
result = asyncio.get_event_loop().run_until_complete(make_result())
print(result)
print_result()
cdef/cpdef
function cannot be a coroutineCython supports coroutines via yield from
and await
only for Python functions. Even for a classical coroutine, a cdef
is not possible:
Error compiling Cython file:
------------------------------------------------------------
cdef call_foo(callback):
print('call_foo')
yield from asyncio.wait_for(callback.foo(), timeout=2)
^
------------------------------------------------------------
testbed.pyx:10:4: 'yield from' not supported here
You are perfectly fine calling a synchronous cdef
function from a coroutine. You are perfectly fine scheduling a coroutine from a cdef
function.
But you cannot await
from inside a cdef
function, nor await
a cdef
function. If you need to do that, as in your example, use a regular def
function.
You can however construct and return a coroutine in a cdef
function. This allows you to await
the result in an outer coroutine:
# inner coroutine
async def pingpong(what):
print('pingpong', what)
await asyncio.sleep(0)
return what
# cdef layer to instantiate and return coroutine
cdef make_pingpong():
print('make_pingpong')
return pingpong('nananana')
# outer coroutine
async def play():
for i in range(3):
result = await make_pingpong()
print(i, '=>', result)
asyncio.get_event_loop().run_until_complete(play())
Note that despite the await
, make_pingpong
is not a coroutine. It is merely a factory for coroutines.