@app.before_server_start async def setup_db(app): app.ctx.db = await asyncpg.create_pool(...) @app.get("/user/<uid>") async def get_user(request): async with request.app.ctx.db.acquire() as conn: return json(await conn.fetchrow("SELECT * FROM users WHERE id=$1", uid))
Consider this practical example from the implied text: python web development with sanic adam hopkins pdf
One of Sanic’s killer features, heavily documented by Hopkins, is app.ctx (application context). Unlike Flask’s thread-local g or request proxies, Sanic’s context is truly asynchronous and isolated. The PDF probably dedicates an entire chapter to the "Shared Context Anti-Pattern," warning against global variables in async code. Instead, Hopkins advocates for attaching database pools, Redis clients, and ML models directly to app.ctx during the @app.before_server_start listener. You simply await
For the reader willing to abandon the comfort of WSGI and the crutch of Flask’s global request proxies, the PDF offers a path to a simpler truth: concurrency is hard, but fighting your framework should not be. With Sanic, the fight ends. You simply await . This essay is a critical analysis of the concepts implied by Adam Hopkins’ work on Sanic. For actual code examples and the latest framework documentation, refer to the official Sanic project documentation and Hopkins’ published writings. Hopkins advocates for attaching database pools