#31637: Registering database connections for cleanup on fork
-------------------------------------+-------------------------------------
Reporter: Aarni Koskela | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* cc: Simon Charette (added)
* stage: Unreviewed => Accepted
Comment:
I think we should do this even if we're moving away from `fork`'ing
internally (e.g. parallel test runner moving to `spawn`) as it's a really
common pitfall when using multiprocessing with the ORM.
--
Ticket URL: <https://code.djangoproject.com/ticket/31637#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.16a88f7b95f9e3ebae4cc1f14dd338eb%40djangoproject.com.
