R
Ray Schumacher
Thanks Larry,
My depth really only gets to ~3:
package
module
module
error_module
and usually not that.
It is shallow, with >hundred methods (mainly serial protocol defs for
LX* telescopes), but it could grow modules, I suppose.
I mainly see its use as an import for other, large apps.
Speed is not an issue here, just clutter, as you'd said.
I also have not seen a written consensus on the "proper" usage of
class variables, if any. I define module vars (some constants), which
I think is reasonable, although these modules are the type with only one class:
port = LXSerial.LXSerial(...)
My rationale of putting one class in its own module is to minimize
giant module files with lots of long classes; I see only a remote
possibility that someone would want call a class without most of the
others as well.
Ray
My depth really only gets to ~3:
package
module
module
error_module
and usually not that.
It is shallow, with >hundred methods (mainly serial protocol defs for
LX* telescopes), but it could grow modules, I suppose.
I mainly see its use as an import for other, large apps.
Speed is not an issue here, just clutter, as you'd said.
I also have not seen a written consensus on the "proper" usage of
class variables, if any. I define module vars (some constants), which
I think is reasonable, although these modules are the type with only one class:
port = LXSerial.LXSerial(...)
My rationale of putting one class in its own module is to minimize
giant module files with lots of long classes; I see only a remote
possibility that someone would want call a class without most of the
others as well.
Ray