On 3/15/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > it's entirely up to you how you set that up. I use the latter form of > imports all the time in my work -- if all the apps are under a single > project directory (which isn't always true), I point the Python path to > the project directory itself, not it's parent.
Another data point: Most of the time I don't actually do the "apps live within your project folder" setup, because I'm usually pulling in reusable apps I've written or that other people have released, so I pull those down into a directory that's directly on my Python path, and then import from there. For example, djangosnippets.org uses two apps -- 'cab' for the snippets part, and 'registration' for the user signups. Neither of those apps lives in the project directory for the site; instead they live elsewhere in a directory that's on my Python path, and I do things like from cab.models import Snippet from registration import views etc. I've found this to be extremely useful for "mixing and matching" different combinations of applications, because then I don't have to worry about imports. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
