summaryrefslogtreecommitdiffstats
path: root/Lib/contextlib.py
Commit message (Collapse)AuthorAgeFilesLines
* Remove markup from docstringNick Coghlan2009-06-231-2/+2
|
* Issue 6288: Update contextlib.nested() docstring to reflect new documentationNick Coghlan2009-06-231-10/+8
|
* Issue 6256: Fix stacklevel in warning message.Raymond Hettinger2009-06-101-1/+1
|
* Deprecate contextlib.nested(). The with-statement now provides this ↵Raymond Hettinger2009-05-291-0/+3
| | | | functionality directly.
* #1748: use functools.wraps instead of rolling own metadata update.Georg Brandl2008-04-301-6/+2
|
* Fix for bug 1705170 - contextmanager swallowing StopIteration (2.5 backport ↵Nick Coghlan2007-11-021-0/+4
| | | | candidate)
* Use try-except-finally in contextlib.Georg Brandl2007-08-231-9/+8
|
* Finish bringing SVN into line with latest version of PEP 343 by getting rid ↵Nick Coghlan2006-05-031-8/+8
| | | | of all remaining references to context objects that I could find. Without a __context__() method context objects no longer exist. Also get test_with working again, and adopt a suggestion from Neal for decimal.Context.get_manager()
* Get rid of __context__, per the latest changes to PEP 343 and python-devGuido van Rossum2006-05-021-8/+2
| | | | | | | | discussion. There are two places of documentation that still mention __context__: Doc/lib/libstdtypes.tex -- I wasn't quite sure how to rewrite that without spending a whole lot of time thinking about it; and whatsnew, which Andrew usually likes to change himself.
* Fix docstring for contextfactory; mentioned old contextmanager name.Brett Cannon2006-04-291-1/+1
|
* Move the PEP 343 documentation and implementation closer to theNick Coghlan2006-04-251-14/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Fix contextlib.nested to cope with exit methods raising and handling exceptionsNick Coghlan2006-04-241-1/+4
|
* Minor clarity edit to contextlib per Guido's request.Phillip J. Eby2006-04-101-2/+2
|
* Fix typos; enhance comments on patch for SF #1462485.Phillip J. Eby2006-04-031-2/+3
| | | | | | --This line, and those below, will be ignored-- M contextlib.py
* Fix SF#1462485: StopIteration raised in body of 'with' statement suppressedPhillip J. Eby2006-04-031-1/+3
|
* Fix contextlib not copying function attributesPhillip J. Eby2006-03-281-0/+1
|
* More extensive comment on __exit__ handling, per Guido's request.Phillip J. Eby2006-03-251-0/+7
|
* Fix a problem with @contextmanager not detecting a broken generatorPhillip J. Eby2006-03-251-1/+4
| | | | | | that yields after a throw(). Make @contextmanager not reraise exceptions, but return a false value in that case instead. Add test cases for both behaviors.
* Um, I thought I'd already checked this in.Guido van Rossum2006-03-101-6/+5
| | | | | | | Anyway, this is the changes to the with-statement so that __exit__ must return a true value in order for a pending exception to be ignored. The PEP (343) is already updated.
* Fix a bug in nested() - if one of the sub-context-managers swallows theGuido van Rossum2006-03-011-1/+4
| | | | exception, it should not be propagated up. With unit tests.
* Updates to the with-statement:Guido van Rossum2006-02-281-0/+138
- New semantics for __exit__() -- it must re-raise the exception if type is not None; the with-statement itself doesn't do this. (See the updated PEP for motivation.) - Added context managers to: - file - thread.LockType - threading.{Lock,RLock,Condition,Semaphore,BoundedSemaphore} - decimal.Context - Added contextlib.py, which defines @contextmanager, nested(), closing(). - Unit tests all around; bot no docs yet.