Hi, I'd like to ask how to organize Django application. To me, structure of project/app is nice idea, however I have problems applying it in practice, so I'd like to ask about best practices.
Problems come, when application structure become deeper and nested. Is it usual to start an application inside application? Django-admin disagree with it. How is it with dependencies? When part of application depends on another, should it be subapplication, or normal top-level application depending on another one? Plus, when django philosophy is to have "application packages", why are templates separated into another directory structure? I'm more familiar (from my personal cherrypy structure) with lib/apps for model, tpl/apps and web/apps separation for M/V/C, but django seem to mixing it together. What are reasons for this and what are best practices for structuring bigger/complicated apps? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
