Dir structure and modules
|Reported by:||Owned by:||Adrian Holovaty|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
These two things are against DRY in Django.
The project directory structure is too long and makes the user repeat the same thing over and over. For example apps/bulletin/model/bulletin.py, apps/bulletin/view/bulletin.py, etc. It would be nice if the user had more control on the directory layout and could instruct Django to use another one (for example apps/bulletin/model.py and apps/bulletin/view.py).
Another problematic thing is the django.models. package which causes that two models in two different apps with an identical name have to have different module_name's. So if I have a model 'Vote' in the 'poll' app and 'Vote' in the 'election' app, one of those has to have a different module_name since django will strangely try to push them both into django.models.votes. So why not make it django.models.poll.vote (why even pluralise it and make it more vague and problematic through the process?).