A Brief History of Python Web Frameworks
summary
Starts at 1989 with HTTP 0.9 and moves through CGI with Apache and mod_cgi, Zope’s all‑in‑one ZODB (powerful but hard to access), CherryPy, TurboGears and Django around 2005, then WSGI’s arrival and WSGI standard that enables interchangeable servers and middleware. Note uWSGI and Gunicorn, Bottle’s “three‑day” origin, the rise of ASGI and WebSockets, Starlette as an Starlette toolkit, and FastAPI + Pydantic using type hints — each entry shows what was built, which servers and ORMs were used, and whether it actually scaled.
AI-written summary · about
chapters (18)
- 0:00Python web frameworks intro
- 1:56HTTP evolution 1989-1997
- 3:41CGI and dynamic web
- 4:47Zope and Python CMS
- 7:55Quixote & Webware alternatives
- 9:41Java servlets vs Python WebKit
- 11:47WSGI modern foundation
- 12:52CherryPy’s pioneering role
- 13:54TurboGears full-stack Rails
- 16:22Django’s admin success
- 17:24Web.py and YouTube
- 18:05Pylons modular revolution
- 19:08uWSGI & Bottle microframework
- 19:50Tornado async renaissance
- 20:12Flask community success
- 21:15ASGI & Django Channels
- 21:59Starlette & FastAPI toolkit
- 23:27Legacy of Python web
related talks
31mHey, Python-Web-Community! What's going on?
18mFrom WSGI to ASGI - Django 3.0
31mInside ASGI The Engine Behind Modern Python Web Frameworks
26mUsing Django as a Micro-Framework: Hacking on the HTTP handlers..
26mInside web framework: intro to the ASGI spec, middleware and apps
58muWSGI, the Swiss Army (MacGyver) knife of deployment
18mPython in Our Home: (R)evolution Yesterday, Today and Tomorrow
31mCreating a WSGI Microframework with PEP 3333