Hi Jacob, Rajeev pinpointed the use case. The company I work for has a large bit of infrastructure built around Django. Our main project consists of 6 apps, each of which has a defined role (with respect to the other apps). One of our apps has quite a few models and quite a bit a logic around those models. The source is over 3000 lines. This amount of code is obviously difficult to manage in one file; one file per model and supporting models (gerunds, etc) would be ideal.
In certain cases I believe developers would find this patch very useful, and very little is added to achieve this additional functionality. Looking at the issue from a broader perspective, I believe people expect to be able to convert Python modules into packages. This was certainly my expectation the first time I tried to factor a models module. - Mark On Wed, Jul 28, 2010 at 10:55 AM, Rajeev J Sebastian < rajeev.sebast...@gmail.com> wrote: > On Wed, Jul 28, 2010 at 10:45 PM, Jacob Kaplan-Moss <ja...@jacobian.org> > wrote: > > On Wed, Jul 28, 2010 at 12:09 PM, Rajeev J Sebastian > > <rajeev.sebast...@gmail.com> wrote: > >> I think it might be useful for people refactoring their ever-growing > models.py > > > > That's maybe part of what I don't understand: I can't ever say I've > > seen a models.py so big that I felt the need to split it up. Or > > rather, I have, but in each case it was better design to break up the > > entire app into a few smaller ones. > > > > I just don't see a problem that, in the very rare case you *do* have a > > models.py that needs to be broken up, you have to manually specify > > app_label. > > I guess thats a different way of working, where you have a lot of smaller > apps. > > It's just boring to repeat the same thing all over the code :D > > Regards > Rajeev J Sebastian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
