Core Team Panel
summary
Proposal for channels: Twisted-based, message-passing 80% real‑time solution aims to add sockets before URL routing and requires a volunteer or funding to land likely around 1.10 not guaranteed Migrtions hitched to a Kickstarter previously Forms can be extracted with moderate work runserver stays development only no production promise A tasks API with backends like Celery and RQ intends to standardize background jobs Composite fields look imminent password validation and new admin styling are landing and a Django Stables registry is being proposed to track package compatibility
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:20Real-time processing and Django Channels
- 3:24Q&A
- 5:34Decoupling Django Forms
- 8:25Production Django runserver alternatives
- 10:28Third-party package philosophy
- 15:02Django 1.9 and beyond
- 18:59Django Stables project
- 20:45REST APIs and Django
- 24:16Django as API-first
- 25:21WebSocket routing challenges
- 26:47Closing
related talks
44mCore Developer Panel
31mReinventing Django for the Real-Time Web
24mLightning Talks
55mWorkshop 1 - Let's Make a Realtime Game with Django Channels
27mTaking Django Async
26mUsing Django 4.2's StreamingHttpResponse and HTMX SSE to provide real time notifications
43mKeynote: A divided web, a review of the role of frameworks
40mTaking Django Async