On Tue, Oct 6, 2009 at 2:26 PM, Serdar Tumgoren wrote:
> I have a set of classes that I've named models.py (following the
> Django convention, though it's not technically a Django project or
> app).
>
> Inside that file, I had initially grouped together a number of
> classes, subclasses and mixin
> I don't think there is a "right" answer to this question. It depends
> on how the classes are used and related to each other. If the Auto
> classes are related or if they are useful to more than one client,
> perhaps you should make an auto_models.py to hold them. If they are
> only useful to ind
Hi everyone,
I was wondering if anyone could offer advice as I try to simplify a
project I've been working on.
I have a set of classes that I've named models.py (following the
Django convention, though it's not technically a Django project or
app).
Inside that file, I had initially grouped toget