Phillip J. Eby wrote:
> At 12:08 AM 4/26/2006 +1000, Nick Coghlan wrote:
>> Secondly, the documentation now shows an example
>> of a class with a close() method using contextlib.closing directly as
>> its own
>> __context__() method.
>
> Sadly, that would only work if closing() were a function.
Nick Coghlan wrote:
> (An idea that just occurred to me in writing this email is "managed
> context". That's a lot less clumsy, and fits with the context manager
> idea.
+1
> Context expressions
> In response to a comment Aahz made, I tweaked the language
> reference to explicitly refer to the
At 12:08 AM 4/26/2006 +1000, Nick Coghlan wrote:
>Secondly, the documentation now shows an example
>of a class with a close() method using contextlib.closing directly as its own
>__context__() method.
Sadly, that would only work if closing() were a function. Classes don't
get turned into methods
On Wed, Apr 26, 2006 at 12:08:47AM +1000, Nick Coghlan wrote:
> However, I made the
> changes below in order to address the conflicts between the alpha 1
> documentation and implementation.
IMHO this set of changes makes the terminology reasonably clear, so
I'm happy with it. I've edited the Wh
I won't call this a resolution yet, since it'll probably be a few days before
I get time to update the PEP itself, and the changes below are based on
pulling together a few different threads of the recent discussion. However, I
believe (hope?) we're very close to being done :)
The heart of the
