Just van Rossum wrote:
> Baptiste Carvello wrote:
>
>> Terry Reedy a écrit :
>>> So I propose that the context maker be called just that: 'context
>>> maker'. That should pretty clearly not be the context that manages
>>> the block execution.
>>>
>> +1 for context maker. In fact, after reading the begining of the
>> thread, I came up with the very same idea.
>
> Or maybe "context factory"?
That would be fine if we used __call__ to retrieve the context manager - but
"factory" is too tightly bound to "factory function" in my mind.
I'm going to try a pass through the docs using "context specifier", which
gives three separate terms:
- context specifier:
An object with a __context__ method that produces a context manager
object to manipulate the runtime context
- context manager:
An object with __enter__ and __exit__ methods that manipulate the
runtime context.
- context (or runtime context):
The actual changes made to the runtime state by the context manager
based on the current state of the context specifier
This removes the ambiguity between "context object" and "runtime context".
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
---------------------------------------------------------------
http://www.boredomandlaziness.org
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
