The project path is incorrectly build, it wipe the namespace

[mleduc]

If by example your django is in an egg like

my.site.project

If you call the django core execution manager with:

mod = __import__('my.site.project')
django.core.management.execute_manager(mod)

Your project will not be found cause the django core is declaring the main DJANGO_SETTINGS_MODULE with:

django.core.management.init:

...
project_directory, settings_filename = os.path.split(p)
if project_directory == os.curdir or not project_directory:
   project_directory = os.getcwd()
project_name = os.path.basename(project_directory)
...
os.environ['DJANGO_SETTINGS_MODULE = '%s.%s' % (project_name, settings_name)
...

The project_name variable represent only the first level of the project egg. It could not work with a multilevel package and we now have to use the variable 'original_settings_path' which is just optional.

The solution maybe to use the special package variable of the settings_mod module.

I attach a patch with this ticket whick correct this problem.

[mleduc]

django.core.management.init.py patch

[Alex Gaynor]

Please use preview.

[James Bennett]

1.2 is feature-frozen, moving this feature request off the milestone.

(and egg support is most definitely a feature request)

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Claude Paroz]

Most of this code is now obsolete. Reopen with current code references if still valid.