Simplifying imports?

[George Sakkis]

"Terry Hancock" <hancock at anansispaceworks.com> wrote:

> On Tuesday 13 September 2005 12:46 pm, George Sakkis wrote:
> > Or even better, forget about the braindead java restriction of one
> > class per file and organize your code as it makes more sense to you.
>
> While this is good sound Python advice, there are good Human-readability
> reasons for keeping a small number of classes per module. Python classes
> certainly may not tend to blossum into the verbosity of their Java
> counterparts, but I've still seen some pretty chunky classes (e.g. in
> the Zope sources).   So, the __init__.py approach and packaging is
> still a good idea.

I agree, and that's what I had in mind with "as it makes more sense to
you". Big fat classes _are_ a good reason to keep them in separate
files, if nothing else, for readability reasons. What's braindead is
that java imposes a rule for what should be at best a good style
guideline.

George