Introduction: The Noisy Ecosystem of Python Web Frameworks The Python web development landscape is often described as a battleground of giants. On one side stands Django, the "batteries-included" behemoth ideal for monolithic applications. On the other, Flask offers minimalist microframework elegance, later refined by FastAPI’s marriage of performance and automatic OpenAPI documentation. Lost in this noise, yet critically important, is Sanic.
Adam Hopkins, the creator and lead maintainer of Sanic, did not write Sanic: Python Web Development as just another tutorial. Reading between the lines of the framework’s evolution, this hypothetical but authoritative PDF serves a singular, disruptive thesis: This essay argues that Hopkins’ work is a polemic against "async-washing" (bolting async onto sync frameworks) and a practical manifesto for building web services that finally leverage Python’s async/await without compromise. Part I: The WSGI Hangover – Why Sanic Exists The first third of Hopkins’ book is likely dedicated to a painful history lesson: the limitations of WSGI. While WSGI served Python faithfully for two decades, it is fundamentally synchronous. Frameworks like Flask and Django, even with async endpoints added later, are at their core WSGI applications. They must spawn multiple worker processes (via Gunicorn) to handle concurrency, leading to a linear scalability problem. python web development with sanic adam hopkins pdf
Consider this practical example from the implied text: Introduction: The Noisy Ecosystem of Python Web Frameworks