Hi Guys,
While trying out a new WSGI handler, that should run fine in the usual
command line "runserver", i noticed that the get_commands() in
managment.__init__ does not look for commands in the top level
directory.
suppose things are set up as follows
/project/
/app1/
/app2/
manage.py
settings.py
....
the get_commands will look into each app to find commands but not the
'project' level. But also if an app defined a "core" command, it does
not 'overload' the core one (i.e. say 'runserver' for instance).
So the proposal is this
1) Add the ability to define a "project" command in the root directory
(which is _not_ app dependent)
2) reverse the load order of get_commands to start from the App -->
Project --> core
i.e.
...
/django/core/management/comands/
blaa.py -- load #3
/project/
/management/
/commands/
blaa.py -- load #2
/app1/
/management/
/commands/
blaa.py -- load #1
the reason why this might be handy is the project an control various
inter-relations between apps and also use some 'other' WSGI handlers
in runserver or different FCGI handlers
thoughts?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
