I think it depends on requirements; not everything has to be a reusable app ! For example, if you have a number of interdependent apps as part of a larger system,and breaking them up makes no sense, housing them under a single package is good practice.
What you should avoid is using the same name as your *project*, i.e. the directory where you have your manage.py and settings.py. That makes it hard to redeploy, not just reuse. On Jan 15, 11:30 am, Sebastian Pawlus <sebastian.paw...@gmail.com> wrote: > Hi > > I've found something like "Top 10 tips to a new Django developer" > > http://blog.dpeepul.com/2009/08/31/top-10-tips-to-a-new-django-develo... > > I'm really blasted by first point "Don’t put project name in the imports". > is this point correct? Django site and core > developershttp://github.com/jacobian/cheeserater/blob/master/urls.pyhttp://code.djangoproject.com/browser/djangoproject.com/django_website/ > > break that rule. > > x_O
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
