On 8/31/07, Davidov <[EMAIL PROTECTED]> wrote: > This means that project should have some knowledge about parent site. > This makes it difficult to move projects from site to site. Also this > violates DRY (you have to write site name again).
For sake of convenience, the tutorial walks you through developing the application inside a subdirectory of the project. Doing so is not necessary, and in fact a reusable application must be developed "standalone" to avoid unnecessary coupling to a single project. > Is there a way to solve this elegant way (without modifying python > modules load path)? Develop the application standalone -- separate from any project -- with the application's module in a directory that's directly on the Python path. Remember that the "project" concept is really a sort of wrapper for defining the applications and settings in use, so it's only technically needed when you want to work with the running application, and there's no need to have all the applications located inside the project's directory; again, the tutorial only does that because it's easier to keep everything in one location when you're just starting out. -- "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 -~----------~----~----~----~------~----~------~--~---
