hi, here are my personal thoughts on the proposals:
On Tue, Oct 18, 2011 at 5:21 PM, Rich Jones <miser...@gmail.com> wrote: > django-admin.py startproject newproj > > should create ./static, ./uploads and ./newproj and ./newproj/ > templates -0 ./static might be common, the others are way too specific. > in ./newproj/settings.py.. > > import os > TEMPLATE_DIRS = ( > os.path.join(os.path.dirname(__file__), 'templates'), > ) +0 i use something similar. i don't like exactly this version, but getting away from static absolute paths is always good > and at the end, the commonly used from local settings import * block. -1 there are too many flavors of that. > I'd also suggest that django-admin.py startproject newapp, if > possible, add the new application to the settings.py file if it can be > done so safely. -1 once the default settings.py is generated, it's my own; i don't want any 'help process' meddling with it. > I would also suggest that when making a new application, the most > commonly used imports are already there in the py files > (render_to_response, HttpResonse, get_object_or_404, etc). 0 i like the error messages when i don't include things. -- Javier -- 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.
