Debugging with asyncio

There are several useful debugging features built into asyncio.

First, the event loop uses logging to emit status messages as it runs. Some of these are available if logging is enabled in an application. Others can be turned on by telling the loop to emit more debugging messages. Call set_debug() passing a boolean value indicating whether or not debugging should be enabled.

Because applications built on asyncio are highly sensitive to greedy coroutines failing to yield control, there is support for detecting slow callbacks built into the event loop. Turn it on by enabling debugging, and control the definition of “slow” by setting the slow_callback_duration property of the loop to the number of seconds after which a warning should be emitted.

Finally, if an application using asyncio exits without cleaning up some of the coroutines or other resources, that may mean there is a logic error preventing some of the application code from running. Enabling ResourceWarning warnings causes these cases to be reported when the program exits.
import argparse
import asyncio
import logging
import sys
import time
import warnings

parser = argparse.ArgumentParser('debugging asyncio')
args = parser.parse_args()

    format='%(levelname)7s: %(message)s',
LOG = logging.getLogger('')

async def inner():'inner starting')
    # Use a blocking sleep to simulate
    # doing work inside the function.
    time.sleep(0.1)'inner completed')

async def outer(loop):'outer starting')
    await asyncio.ensure_future(loop.create_task(inner()))'outer completed')

event_loop = asyncio.get_event_loop()
if args.verbose:'enabling debugging')

    # Enable debugging

    # Make the threshold for "slow" tasks very very small for
    # illustration. The default is 0.1, or 100 milliseconds.
    event_loop.slow_callback_duration = 0.001

    # Report all mistakes managing asynchronous resources.
    warnings.simplefilter('always', ResourceWarning)'entering event loop')

When run without debugging enabled, everything looks fine with this application.

$ python3

  DEBUG: Using selector: KqueueSelector
   INFO: entering event loop
   INFO: outer starting
   INFO: inner starting
   INFO: inner completed
   INFO: outer completed

Turning on debugging exposes some of the issues it has, including the fact that although inner() finishes it takes more time to do so than the slow_callback_duration that has been set and that the event loop is not being properly closed when the program exits.

$ python3 -v

  DEBUG: Using selector: KqueueSelector
   INFO: enabling debugging
   INFO: entering event loop
   INFO: outer starting
WARNING: Executing <Task pending coro=<outer() running at> wait_for=<Task pending coro=<inner()
running at> cb=[<TaskWakeupMethWrapper
object at 0x106e0d288>()] created at>
cb=[_run_until_complete_cb() at
.../lib/python3.7/asyncio/] created at
.../lib/python3.7/asyncio/> took 0.001 seconds
   INFO: inner starting
   INFO: inner completed
WARNING: Executing <Task finished coro=<inner() done, defined at> result=None created at>
took 0.101 seconds
   INFO: outer completed