Best practice for large source code projects

[faulkner]

several of my programs are thousands of lines long, and i don't think
they're extravagantly large.
i'd say you should use modules the same way you use classes and
functions: to separate code logically.
if it makes sense to think of a group of statements as a function, you
make it a function. if it makes sense to think of a group of functions
as data as a single object, you make a class. if it makes sense to
think of a collection of classes and functions and data as a collective
unit, make a module. and so on for packages.
if it makes sense for a single function to be hundreds or thousands of
lines long, so be it.
follow the modern poet's rule: ignore restrictions that don't make
sense, and follow closely the restrictions you choose.


dhable at gmail.com wrote:
> I'm developing a web system and based on some patterns I've seen
> elsewhere, I made a single  file (model.py) to hold all of the
> functions and classes that define the model porition of the
> application. Hence the code in the controller looks like:
>
> import model
>
> def Display(req,id):
>   # ....
>
>
> It works and things make sense to me. Yet, I feel uneasy that my
> model.py file is starting to approach 500 lines. What's the best
> practice or community opinion on this? Do I keep everything in a single
> file or do I start dividing things into separate files?
> 
> TIA