#27937: Potential issue with field.queryset._result_cache persisting
-------------------------------+--------------------------------------
Reporter: Luke Benstead | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Luke Benstead):
Unfortunately I don't have time to look into this too much, but I've
attached a patch which updates the tests to check for an empty
_result_cache after form instantiation. You can see that only one of the
two tests fails (depending on order) because the _result_cache persists
across tests.
--
Ticket URL: <https://code.djangoproject.com/ticket/27937#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.674439fcac0393ef05400ba31bd41cbc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
