#37066: Async generator `aclose()` deferred to loop shutdown at `async for` call
sites that don't use `contextlib.aclosing`
--------------------------------------+------------------------------------
Reporter: Thomas Grainger | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Uncategorized | Version: 6.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Simon Charette):
* needs_better_patch: 0 => 1
* stage: Unreviewed => Accepted
Comment:
Note that there are also known problems with some sync iterators holding
resources until garbage collection such as `QuerySet.iterator`
[https://code.djangoproject.com/ticket/37000#comment:5 when using server-
side cursors] which might also warrant some documentation adjustments.
I think it's worth treating these as separate issues but I figured I'd
point out that it's not only an async/IO problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/37066#comment:2>
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/0107019dd497397a-2225dc1b-9c33-4ebf-8d2d-19f3f5246095-000000%40eu-central-1.amazonses.com.
