#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 carljm):
I guess the question is whether the potential brokenness of module
reloading is Django-specific, or inherent to module reloading in Python.
If the latter, it's more like we're saying "here's a feature of Python
that has some gotchas, and we think the gotchas are bad enough that the
feature shouldn't be in Python at all, so we're going to make it
impossible to use it with Django."
Module reloading _is_ inherently problematic in Python anytime one module
holds references to anything from another module. But it's perhaps a
little worse with Django, since models are highly likely to hold
references to one another?
If this were hard to implement, I think it'd be an easy choice not to. But
in fact, it's just slightly relaxing a one-liner check.
--
Ticket URL: <https://code.djangoproject.com/ticket/23621#comment:12>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.9f3d451a28cb0a663f08a3ab8e36ebb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
