#31626: Add asgi support to runserver
---------------------------------+-------------------------------------
Reporter: Joshua Massover | Owner: nobody
Type: New feature | Status: closed
Component: HTTP handling | Version: 3.0
Severity: Normal | Resolution: needsinfo
Keywords: runserver, asgi | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* keywords: => runserver, asgi
* component: Uncategorized => HTTP handling
* stage: Unreviewed => Accepted
Comment:
OK, let's accept this as a new feature.
The suggestion in the forum thread is to detect if Daphne or uvicorn or
... is installed and then use that.
In the draft PR looks like importing Daphne in a `try` block, which I´m
not sure about at all.
Is there a way we can detect the asgi server without hard-coding imports?
I'd imagined a server based off of Python's `http.server`, as we have for
WSGI, either in Django or `asigref` as appropriate.
In the meantime, 3.1 could probably do with some docs, saying to install
channels (to use it's runserver) or uvicorn (which has a `--reload`
option).
--
Ticket URL: <https://code.djangoproject.com/ticket/31626#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.555f751e55920ce0761889116e5c19ae%40djangoproject.com.
