I'm +1 on this. Project conventions tend to be the biggest problem when adding new people to the team, especially when it comes to configuration management - everyone has their own way.
It would be great if there will be at least an official list of best practices on building Django project layout. On Mar 11, 7:14 am, Simon Litchfield <si...@s29.com.au> wrote: > Who votes we should come up with a django-blessed 'official' default project > layout / directory structure? > > Might sound like a triviality, but sometimes it's the little things..... > > 1. Newcomers -- startproject throws 9/10 into confusion and results in a > messy first few projects. > > 2. Gurus -- each have their own way, what a waste, not DRY. > > 3. The new breed of django hosting platforms that are on their way -- gives > them something to base their tools on. > > Why not have a standard way, standard tools, etc etc- built in, batteries > included. DRY. > > Whether it be a plain old manage.py-friendly directory layout, something > virtualenv+pip powered, maybe something like Lincoln Loop's startproject > style, Eric Holscher's, or whatever. Lets not go too nuts on directories > though, they get tiring (especially in textmate) > > 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
