sethmlarson / pycon-async-sync-poster

An example project which demonstrates how to use some new tools to more easily maintain a codebase that supports both async and synchronous I/O and multiple async libraries.

Designing Libraries for Async and Synchronous I/O

An example project which demonstrates how to use some new tools to more easily maintain a codebase that supports both async and synchronous I/O and multiple async libraries.

Meet the Tools

• Supporting Sync and Async:
  • unasync
• Supporting multiple Async libraries:
  • sniffio
  • anyio

The library itself is a massive contrived example that doesn't do anything useful. The important part is seeing the different libraries and constructions all working together!

How the Project is Structured

There are three different categories of code that go into creating a project that supports sync, asyncio, trio, etc:

Code that directly interacts with I/O APIs (sockets, threads, asyncio)

Code that directly interacts with individual APIs that are different across the sync, asyncio, and Trio live under backends/. The function get_backend() can either return a SyncBackend which uses a threadpool for parallelism and time.sleep or return a flavor of AsyncBackend depending on which library sniffio detects.

Code that needs to be async but doesn't directly interact with I/O APIs

This is where the bulk of your libraries public API code will probably live. Typically you will write structural code here which call into your Backend code written above.

You want to try to fit as much of your API code here as you can so you can benefit from unasync generating the synchronous half automatically. When writing this code you'll have to keep in mind what the resulting generated code will look like though.

Code that doesn't have I/O

Code that doesn't need to touch I/O at all like enums, dataclasses, helpers, etc. Also things like importing your AsyncAPI and SyncAPI to make them accessible to users.

Interesting Places to Look

• IS_ASYNC detection of whether we're in _async/ or _sync/
• Lazily load the backend so AsyncSleeper can be used in the global scope
• Backend Detection using Sniffio
• Unasync called within setup.py to generate _sync/ code on dist build

The Library in Action

import asyncio
import sleepy

# === Asyncio ===

sleeper = sleepy.AsyncSleeper()

async def main_asyncio():
    await sleeper.sleep_a_lot(3)

asyncio.run(main_asyncio())

# === Trio ===
# python -m pip install trio

import trio

sleeper = sleepy.AsyncSleeper()

async def main_trio():
    await sleeper.sleep_a_lot(10)  

trio.run(main_trio)

# === Sync ===

sleeper = sleepy.SyncSleeper()

def main_sync():
    sleeper.sleep_a_lot(5) 

main_sync()

License

CC0-1.0