Application module imported twice when running development server

[rlz]

I use Django 1.2.3.

I've created a new django project testproject and a new django application test.
I've put the allication inside settings.py, then put only one line of code in test/init.py:

print 'loaded'

And import the applicaton module from application urls.py:

import test

In result the line 'loaded' was printed twice.

This behaviour lead to error in my real project.

[Keryn Knight <keryn@…>]

Is this not a function of the project/application being loaded once per process?

What environment are you experiencing this under? manage.py runserver or perhaps a mod_wsgi setup?

[anonymous]

Replying to Keryn Knight <keryn@kerynknight.com>:

Is this not a function of the project/application being loaded once per process?

What environment are you experiencing this under? manage.py runserver or perhaps a mod_wsgi setup?

I used manage.py runserver

[Natalia Bidart]

Confirmed the double import. After some simple, I can confirm that manage.py:execute_manager() is called twice.

The re-entrance point is located within the Command implementation for runserver:

django/core/management/commands/runserver.py(99)

where the autoreload.main(inner_run) method is called. This method spawns a new process that re-executes 'execute_manager()', and this causes the app to be imported twice (since the second time the app is imported is from a different thread, so the import is really executed twice).

I'm not sure how this should be fix, so I'll mark this as 'design decision needed'.

[Karen Tracey]

Loading an app's __init__.py more than once is not a bug. An app should not be coded to expect that its __init__.py will run once and only once. If you have code the must run only once (guessing here since the original report does not actually describe what problem resulted from this behavior) then you need to ensure that happens by some other method than simply putting it in __init__.py and expecting that it will only get loaded once.

[ssadler@…]

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.

[anonymous]

TicketClosingReasons/DontReopenTickets

[Marcin Nowak]

Yes, this is a bug and still exists for 1.8.6. For example - the loggers are initialized twice.