Re: One module per class, bad idea?

[Isaac Rodriguez]

>   make the import statements look good.


You can still make your import statements look good and have one class
per file, that's one of the __init__.py wonderful features.

Also, C++ support stand alone functions and the rule is to organize
classes and their interface (functions that operate in objects of the
class are considered part of the interface) in their own module.

I will like to understand why this will not be a good idea for python,
other than to make beautiful import statements that is.

Thanks,

- Isaac.

-- 
http://mail.python.org/mailman/listinfo/python-list