Don't worry, that checking looks only so large because one file (in
Experimental) was converted from spaces to tabs (Webware/your standard)
and every line is reported as changed. The rest is mostly white space,
word wrapping (I think it makes sense to word wrap at max 80 chars). I
didn't change anything in the real code.
No, I didn't want the code to have my smell, but to make it readable and
follow the conventions in the (your) Webware StyleGuidelines and the
docstring conventions (PEP 257) which says, for instance:
The docstring is a phrase ending in a period. It prescribes the function
or method's effect as a command ("Do this", "Return that"), not as a
description; e.g. don't write "Returns the pathname ...".
I agree that in this case it may be nit-pick, but following a certain
style makes it better readable and make sure the docstrings can be
parsed by tools like epydoc. The installer already creates colorized
source files, pydocs and summary files as part of the Webware online
docs. For creating the summary files, for instance, it is important that
double ## are used for categories only and not for ordinary comments.