That's usually a bad sign when other programmers start naming saints when reviewing your code :-). I have similar code explosion issues in a models.py file in a site I'm building.
What's the best dangothonic way to break up models.py or views.py for that matter. 1. Create a models.py or views.py at the top level that does a bunch of imports? Explicitly or progrmmatically by looping over files? 2. Expose the hierarchy to the caller. Ex: from my_app.models.my_model import MyModel 3. Break up the whole app into smaller apps? Still trying to figure out a good way to determine what should be a separate app. If you have a relathionships like Publishers -> Books, and Authors -> Books should you try to break out Books, Authors, and Publishers as separate apps? Brian Schott bfsch...@gmail.com On Dec 5, 2011, at 5:18 AM, Håkon Erichsen wrote: > - Holy mother of god, that's a huge view file! I would advice to slice it > into logically separated files, and put this in a directory called "views", > everything doesn't have to be in views.py! > -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
