Why NOT only one class per file?

Hendrik van Rooyen mail at microcorp.co.za
Sat Apr 7 10:28:03 CEST 2007

 "Bart Willems" <b.r.willems at gmail.com> wrote:

> Steven D'Aprano wrote:
> > On Wed, 04 Apr 2007 14:23:19 -0700, Chris Lasher wrote:
> > 
> >> A friend of mine with a programming background in Java and Perl places
> >> each class in its own separate file in . I informed him that keeping
> >> all related classes together in a single file is more in the Python
> >> idiom than one file per class. He asked why, and frankly, his valid
> >> question has me flummoxed.
> > 
> > 
> > Hah! Writing one class per file is for wimps! When I program, I write one
> > *method* per file, then import them and build the class at runtime.
> > 
> > I have a friend who writes one *line* per file, then pulls them all
> > together with exec(), but that's just being stupid.
> > 
> > 
> > 
> I guess you're one of those sissies who uses EDLIN as an editor.
> REAL programmers use COPY CON: ... :)

Naaah.. Real programmers fill in their coding sheets using
indelible ink in their fountain pens, and then send them off 
to be punched and verified.

None of this weak minded backspace stuff for us...

- Hendrik

More information about the Python-list mailing list