#31182: Asynchronous Support in 3.0 should clearly state what is and is not
supported
-----------------------------------------+------------------------
Reporter: Josh Smeaton | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 3.0
Severity: Normal | Keywords: async
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 1 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
https://docs.djangoproject.com/en/3.0/topics/async/ begins with the
following text:
> Django has developing support for asynchronous (“async”) Python, but
does not yet support asynchronous views or middleware; they will be coming
in a future release.
Unfortunately, I don't think this is a clear enough message to the
community that they can't *really* use async in Django yet for the
majority of projects that users are going to be working on.
I've had several people at work ask me about the support, and there have
been a number of threads on django-developers mailing list asking how they
can start using async in Django today.
We should clear up the documentation to properly state what can and can
not be used asynchronously. Perhaps we could document an expected timeline
so that users can get a feel for when they may be able to start using
async in Django, without having to refer to the DEP (which is excellent,
but dense for those that want the 10,000 foot view) - but I'm less sure
about setting those expectations.
--
Ticket URL: <https://code.djangoproject.com/ticket/31182>
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/051.5898220cd10babb6ae0e562b6fddaf22%40djangoproject.com.
