#14606: Application module imported twice when running development server
-------------------------------------+-------------------------------------
Reporter: rlz | Owner: nobody
Type: Uncategorized | Status: reopened
Component: Core (Other) | Version: 1.2
Severity: Normal | Resolution:
Keywords: runserver | Triage Stage: Design
Has patch: 0 | decision needed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by ssadler@…):
* status: closed => reopened
* severity: => Normal
* type: => Uncategorized
* easy: => 0
* ui_ux: => 0
* resolution: invalid =>
Comment:
I disagree with the decision to close this ticket. I'm trying to override
the admin site, by creating an instance at module level, the same way as
is done in django.contrib.admin. It's not working because the module is on
the INSTALLED_APPS list as as such gets initialized more than once,
causing it to have inconsistent state. I think that the repeated
instantiation goes against default Python semantics and also the principle
of least surprise, so I'll re-open it for consideration.
--
Ticket URL: <https://code.djangoproject.com/ticket/14606#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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
