On Jan 16, 2007, at 17:52, David Abrahams wrote:
For me, Django doesn't seem to be delivering on its promise to allow me to build a collection of apps and organize them in different combinations into multiple Django projects, and the documentation I can find doesn't really give any clues about best practices for project organization. One problem is that the name of the Django project folder (and thus root module) always seems to creep into the code in the app-specific directories. Any insight you can offer would be appreciated.
in most cases (all for me so far) you can omit the project name. I actually ran into some problems while deploying with mod_python when mentioning the project name in urls. conf and in some import statements. it's all about the python-path :) I always use e.g app_name.models.bla instead of project_name.app_name.models.bla everywhere now At does seem a bit weird, that in many tutorials and the Documentation the project name is always creeps in. I guess it's bad practice when trying to decouple an app from specific projects. I agree that there should be a chapter on best decoupling practaces in the docs.
decoupling url.confs: http://www.djangoproject.com/documentation/0_91/ tutorial3/#decoupling-the-urlconfs
Thanks, -- Dave Abrahams Boost Consulting www.boost-consulting.com >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
