Question about the project structure...

[gmeans]

I was wondering the reasoning behind making the project root a python module vs. following Django's default of making a package within the root for configurations and site level things?

It definitely seems a lot cleaner, but I wasn't sure if this would evolve to eventually match what Django is doing or if this will be the way moving forward?

Or if maybe this template existed before Django made the change and there was no need to change it?

Thanks!

[pydanny]

I hope this doesn't come across the wrong way, but the reasoning behind the project structure is because I like the way it is organized. Myself and others find it useful on both large and small projects. I found Django's default template project rather simplistic in approach, good for beginner projects, not so good for when things get really going.

cookiecutter-djangowill continue on this path going forward.

FWIW, others have created cookiecutter-powered Django project templates that follow other patterns. You can find them by searching for cookiecutter and django on GitHub. ;)

[gmeans]

It was really just a question because I noticed it was different. Knowing you wrote two scoops had me wondering if there was a reason behind it. Perhaps there was some kind of best practice that was evolving.

Thanks for the reply!