On 4/13/07, Anders Olsson <[EMAIL PROTECTED]> wrote: > portable and decoupled from the project where it is used. But doesn't > the project being the top level python package make it almost > impossible to move an app from a project to another without modifying > the import statements?
If you insist that all applications must live inside the project directory, yes. But Django doesn't insist on that; it's convenient when starting out with Django to keep everything in one place, and so long as you have only one or two apps it works well. As you progress onward, you'll probably find yourself more and more using apps distributed around the filesystem with Python paths that aren't dependent on the project name/location. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
