* Russell Keith-Magee <[email protected]> [130507 18:40]: > On Wed, May 8, 2013 at 10:01 AM, Tim Johnson <[email protected]> wrote: <..> > Example > > cd my/shiny/new/django/project > > django-admin.py startproject myproj > > mkdir apps > > cd apps > > manage.py startapp myapp1 > > > > I can't imagine any issues with that, but if anyone were to, please > > let me know your opinion. > > > > As long as you can set up the PYTHONPATH so that the modules can be > imported, there's no issues with this approach. A Django "App" is just a > Python module. As long as it can be imported, you can use it. In fact, Great. And of course, with imp, modules can be 'imported' in a fine-grained fashion.
> you'll find some people who advocate for keeping your "apps" directory > completely separate from your project directory, to emphasise the fact that > in order to maximise reusability, the app should be completely independent > of your project. :) Great minds run the in the same gutter. > The only real restriction is a django-related namespace issue -- you can't > have two apps with the same name, even if they have different fully > qualified module paths (i.e., you can't have my.little.admin and > django.contrib.admin in the same project because they both have an app name > of "admin"). Understood. Thank you Russell -- Tim tim at tee jay forty nine dot com or akwebsoft dot com http://www.akwebsoft.com -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
