who writes:
Here is batch 2, as a big collection of CVS context diffs.
Along with moving comments into docstrings, i've added a
couple of missing docstrings and attempted to make sure more
module docstrings begin with a one-line summary.
I did not add docstrings to the methods in profile.py for
fear of upsetting any careful optimizations there, though
i did move class documentation into class docstrings.
The convention i'm using is to leave credits/version/copyright
type of stuff in # comments, and move the rest of the descriptive
stuff about module usage into module docstrings. Hope this is
okay.
o the initial comment is wrong: creating messages is already
implemented
o Message.getbodytext: if the mail or it's part contains an
empty content-transfer-encoding header, the code used to
break; the change below treats an empty encoding value the same
as the other types that do not need decoding
o SubMessage.getbodytext was missing the decode argument; the
change below adds it; I also made it unconditionally return
the raw text if decoding was not desired, because my own
routines needed that (and it was easier than rewriting my
own routines ;-)
proper argument
* Lib/{bdb,cmd,pdb}.py: Mods by Rickard Westman: No longer barfs
on lambda:s (outputs "<lambda>" as the function name); "a(rgs)" in
pdb now works; help messages added to pdb (lifted from pdb.doc).
Also, "h pdb" calls pdb.help(). cmd.do_help() displays topics on
a nicer way (I think). Also, topics for which there is a help_
method, but no do_method (like "pdb" above) are displayed in a
special way. My own mod: fix break on function to also support
methods.
multifile.py: added readlines() and read() methods
mimetools.py: mimetools.py: added functions to encode/decode standard MIME
Content-transfer-encoding types (as well as uuencode)
rfc822.py: Accept lines ending in CR LF as well
