You must *never* assign exc_info() (or sys.exc_info()[2] or
sys.exc_traceback) to a variable unless you also unassign it in a
finally or you'll generate a circular reference in the stack causing
all kinds of interesting things to get leaked.

mind empty tuples or lists.

doesn't mind false bodies.

Did I break anything? :)

Also changed xml-rpc handling so that index_html is not used.

connected to the database before doing subtransaction tricks.

children.

the standard logging facility.

can provide a disctionary whos items are added to the request.
This makes it alot easier to test methods from the command line that
use file upload.

BODY directly on init, which is too expensive).

db's.

some of the inquiry calls on DB objects should be available on
Connection objects to take subtransactions into account.)

registered so far.

error in non ZODB3 installations.

Added a format_exception method.  This is essentially the method
used by the ZPublisher exception handler and has the nice feature
of showing object __names__ and __traceback_info__.  It is useful
in back-end log handlers *and* in other applications that want to
display tracebacks.

Added output of exception info to the stupid logger.

with orther developers without bumping into each others ports.

self.aq_parent.this(), instead of just self.aq_parent, so we're sure
to get beyond doggone W wrapper objects.

self.getRolesInContext() when object is specified, which does The
Right Thing.