Hi All, On Sunday, 30 December 2012 22:10:24 UTC+1, Stephen McDonald wrote: > > I'm sure we'll update it at some point, there just hasn't been any reason > to other than to keep up to date with Django's approach - eg it works fine > as is right now, so it hasn't been a priority. >
On Mon, Dec 31, 2012 at 7:16 AM, Rodney Morison <[email protected]<javascript:> > > wrote: > >> In my most recent mezzanine site build one of the devs asked why we're >> using the "old" django layout and not the new, i.e., old = "settings and >> urls at the PROJECT_ROOT" and new = "settings and urls >> in PROJECT_ROOT/PROJECT_ROOT". Are there any thoughts/plans at changing the >> default layout for the mezzanine-project template? >> > This is a fairly old thread but seems the best place for my enquiry... I too would prefer the new layout. As such, I've been looking at Mezzanine's version of `manage.py`. Specifically these lines: # Corrects some pathing issues in various contexts, such as cron jobs, # and the project layout still being in Django 1.3 format. from settings import PROJECT_ROOT, PROJECT_DIRNAME os.chdir(PROJECT_ROOT) sys.path.insert(0, os.path.abspath(os.path.join(PROJECT_ROOT, ".."))) In usual case I'm invoking manage.py from PROJECT_ROOT so the chdir is a noop. If I correct the `os.environ.setdefault("DJANGO_SETTINGS_MODULE", settings_module)` call, I also can't see when adding the parent directory to sys.path is going to do anything. (I generally pass the settings module in at the command line anyway.) I'm tempted then to just move everything into the new layout. Am I missing something? Will anything (i.e. something non-obvious) blow-up here? Thanks! — Carlton -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
