#23621: Module autoreloading doesn't work due to some checks while loading an
app
-------------------------------+--------------------------------------
Reporter: pashinin | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.7
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 aaugustin):
Going from "fails silently with subtle and inconsistent effects" to "fails
loudly with an exception" doesn't count as a regression in my book :-)
When you used `reload()` in Django 1.6, there was no guarantee that you
ended up in a consistent state. Specifically, accessing related model
instances could return an obsolete copy of the model class. And I'm
wondering if the change proposed here couldn't make that kind of subtle
bugs possible again.
--
Ticket URL: <https://code.djangoproject.com/ticket/23621#comment:9>
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/066.12d1ed9b7fb07f8edb5a2a463e52e793%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
