On 5/30/07, Luper Rouch <[EMAIL PROTECTED]> wrote: > 2. import bar.module > the application is more portable, but its path has to be included in > PYTHON_PATH (at least under mod_python)
I generally opt for this one, but with one caveat: I almost *never* place applications directly inside the project directory. It's true that the tutorial involves an app that's created inside the project directory, and that's useful for giving a quick introduction to Django (and hence for the tutorial), but once you're writing multiple applications which may be shared among multiple projects, having the applications be "independent" and live somewhere directly on the Python path (say, in site-packages or a similar location local to your user account) is far more useful and encourages looser coupling. It also has the helpful side effect of removing any questions about how to handle 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 -~----------~----~----~----~------~----~------~--~---
