> 4. Finally, why the heck is everything stuffed into an init file?
> ewwwww. :-)
I'm new to python (so that's probably the right thing) but the first
time I looked at TG source code I wondered why __init__.py files
contains so many thing instead of exposing only the package things
people need to import, I like how CatWalk does this for example:
Anyway I'm sure there is a good reason for this.
Could simply be a matter of "first we get it to work, then we worry about making it pretty". The Old Me would wrinkle his prudish nose at that, but the New Me has Learned To Quit Worrying and Learned to Love (bits of) Agile Development Philosophies. :o)
Seriously, once it is stable and solid (it IS pretty new and hasn't got a lot of 'face time' yet so no offense, anyone!) then pitch in and provide patches to polish it up if one feels so inclined, with an eye towards Kevin's coding guidelines.
Which reminds me, I need to actually go out there and play with it. So few hours, so many toys ...
--
"Things fall apart. The Center cannot hold."
- Life as a QA geek, in a nutshell.
Best,
Jeff
