On 16 déc, 22:35, Bill Freeman <ke1g...@gmail.com> wrote: (snip helpful technical answer) > But. java practice notwithstanding, there is nothing wrong with having > several models in one models.py module, so why fight against the > design of django? If your collection of models is truly so complex > that they should be separated into more than one module, then perhaps > your app is too complex, and should be refactored into multiple > applications.
What I would I've said not more than a couple weeks ago - but my current project has a "core" app's models file that starts being a bit to big for my tastes[1], and yet it really wouldn't make any sense breaking it into multiple apps. [1] currently 970 LOCs, and I just have the basic models structures and only one custom manager defined yet, so I know there will be more to come. YMMV but I don't like modules growing much bigger than 1 to 1.5 KLOC. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
