#31182 closed Cleanup/optimization (fixed)
Asynchronous Support in 3.0 should clearly state what is and is not supported.
| Reported by: | Josh Smeaton | Owned by: | Adam Johnson |
|---|---|---|---|
| Component: | Documentation | Version: | 3.0 |
| Severity: | Normal | Keywords: | async |
| Cc: | josh.smeaton@…, Adam Johnson, Andrew Godwin | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Change History (5)
comment:1 by , 5 years ago
| Cc: | added |
|---|
comment:2 by , 5 years ago
| Cc: | added |
|---|---|
| Needs documentation: | unset |
| Summary: | Asynchronous Support in 3.0 should clearly state what is and is not supported → Asynchronous Support in 3.0 should clearly state what is and is not supported. |
| Triage Stage: | Unreviewed → Accepted |
| Type: | Uncategorized → Cleanup/optimization |
comment:3 by , 5 years ago
| Has patch: | set |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
We definitely need to improve the docs here. Happy to review any patches.