#36964: Documentation incorrectly states that persistent connections don't work
with runserver
-------------------------------------+-------------------------------------
Reporter: Adam Sołtysik | Owner: Youssef
Type: | Tarek Ali
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 5.2
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Youssef Tarek Ali):
* has_patch: 0 => 1
* owner: (none) => Youssef Tarek Ali
* status: new => assigned
Comment:
I have assigned this to myself and drafted a documentation update. The new
wording clarifies that persistent connections do work for sequential
requests in the development server, while noting that they are reset upon
auto reload and that concurrent requests still trigger new threads.
Verified the build locally with make html.
PR: https://github.com/django/django/pull/20825
--
Ticket URL: <https://code.djangoproject.com/ticket/36964#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 visit
https://groups.google.com/d/msgid/django-updates/0107019cb52e1c3d-9deda29a-e4fd-4c28-877c-7635105daec4-000000%40eu-central-1.amazonses.com.
