Re: __init__.py file executed twice ?
On Wed, Dec 8, 2010 at 4:52 PM, martvefun <martvefun@gmail.com> wrote:
> Hello,
>
> I'd like to start some threads when the server launch to listen to
> events (I'm doing message passing).
>
> To do so, I guess I should be using the __init__.py file at the root of
> my project (by the way, what's the used of the other __init__.py files
> in the apps)
>
> I've tried with a simple test by only having 'print "starting server"'
> into the file and the result is :
>
> $ python manage.py runserver
> starting server
> starting server
> Validating models...
> 0 errors found
>
> Django version 1.2.3, using settings 'website.settings'
> Development server is running at http://127.0.0.1:8000/
> Quit the server with CONTROL-C.
>
> Why the file is executed twice ? I don't want to have twice the same
> threads.
>
> Thank you
>
> mart
>
__init__.py files aren't executed at the start of programs, the
presence of them denotes that a directory is a python module, and the
__init__.py is executed when that module is first imported under a
particular name.
Do you have a structure like this:
project
├── __init__.py
├── app1
│ └── __init__.py
└── app2
├── __init__.py
└── models.py
and import from project.app2.models and from app2.models? That would
cause app2's __init__.py to be executed twice.
Cheers
Tom
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home