http://docs.python.org/whatsnew/2.6.html#writing-context-managers
penultimate item in "A high-level explanation": <quote>
If BLOCK raises an exception, the __exit__(type, value, traceback)() is called 
</quote> has extra () after the argument list - this appears to say that __exit__ should return a callable, that shall be called with no parameters.  Fortunately, later example code reveals that __exit__ simply returns true or false.

http://docs.python.org/whatsnew/2.6.html#the-contextlib-module
after the first code block: <quote>
The contextlib module also has a nested(mgr1, mgr2, ...)() function 
</quote> again, stray () after parameter list.
After the next short code snippet: <quote>
Finally, the closing(object)() function returns ...
</quote>

Fixed in r78182.

The third change removes the early uses of "object" from:
<quote> Finally, the closing(object)() function returns object so that it can be bound to a variable, and calls object.close at the end of the block. </quote>
leaving the last use (object.close) as a dangling reference.
So either revert this part of the fix and change :func:`closing(object)` to just ``closing(object)`` or follow up the present change by changing <quote> and calls :meth `object.close` at the end </quote> to <q> and calls the argument's :meth:`close` method at the end </q>

Thanks, should be fine now in r78188.

Nice :-)