> IMHO the project namespace is a useful one to keep around. If you > lose the project name space, then you risk polluting your python path > with a lot of generic 'urls' modules, among other things.
I don't understand why in tutorial all imports contain project name. I think this is wrong position. In my case I've got one project named "engine" and three sites using it. If I used import containig "engine" I would place every site into the folder with the same name, but it's inconvenient(I think). My idea is to view site as a number of apps. Each app separated from others and keeps anything it needs in its own namespace. What do you think about it? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
