On 8/24/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Because of this, "project.apps.application.module" should work and it > does for me. But, this isn't ideal since I do want there to be a > dependency on the project name in my apps that I want to be able to > share and drag-and-drop into multiple projects. > > So, what is the best practice for handling this? Putting your project > directory in the path and using "apps" like Rob has done? (I missed > that instruction if it was in the install guide) Or is there another > suggestion?
If you want to decouple apps (to be able to share them among projects), the best practice is to create a separate package that contains only apps. This is the way we do things at World Online. We have an "ellington" directory within site-packages, and it contains every one of our custom Django applications. Then we have a "worldonline_settings" directory, also within site-packages, that contains all the settings for our various Django installations. The directory structure created by "django-admin startproject" is intended to be a quick-start thing, not a long-term best practice. Obviously, putting apps within the directory with your project name couples the app to the name of your project. I figured it'd be easier for beginners this way, but I'm totally open to changing things. I just didn't want the tutorial to be as complex as "First create a place for your apps. Then create a place for your settings. Then create an app..." Suggestions welcome! Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
