Move the PEP 343 documentation and implementation closer to the

terminology in the alpha 1 documentation.

 - "context manager" reverts to its alpha 1 definition
 - the term "context specifier" goes away entirely
 - contextlib.GeneratorContextManager is renamed GeneratorContext

There are still a number of changes relative to alpha 1:

  - the expression in the with statement is explicitly called the
    "context expression" in the language reference
  - the terms 'with statement context', 'context object' or 'with
    statement context' are used in several places instead of a bare
    'context'. The aim of this is to avoid ambiguity in relation to the
    runtime context set up when the block is executed, and the context
    objects that already exist in various application domains (such as
    decimal.Context)
  - contextlib.contextmanager is renamed to contextfactory
    This best reflects the nature of the function resulting from the
    use of that decorator
  - decimal.ContextManager is renamed to WithStatementContext
    Simple dropping the 'Manager' part wasn't possible due to the
    fact that decimal.Context already exists and means something
    different. WithStatementContext is ugly but workable.

A technically unrelated change snuck into this commit:
contextlib.closing now avoids the overhead of creating a
generator, since it's trivial to implement that particular
context manager directly.
This commit is contained in:
Nick Coghlan 2006-04-25 10:56:51 +00:00
parent 327ea38cc4
commit a7e820a408
7 changed files with 165 additions and 141 deletions

View file

@ -2173,7 +2173,7 @@ for name in rounding_functions:
del name, val, globalname, rounding_functions
class ContextManager(object):
class WithStatementContext(object):
"""Helper class to simplify Context management.
Sample usage:
@ -2249,7 +2249,7 @@ class Context(object):
return ', '.join(s) + ')'
def __context__(self):
return ContextManager(self.copy())
return WithStatementContext(self.copy())
def clear_flags(self):
"""Reset all flags to zero"""