Searched refs:ExitStack (Results 1 – 20 of 20) sorted by relevance
354 .. class:: ExitStack()363 with ExitStack() as stack:432 Transfers the callback stack to a fresh :class:`ExitStack` instance440 with ExitStack() as stack:459 to :class:`ExitStack`, that supports combining both synchronous and505 The primary use case for :class:`ExitStack` is the one given in the class512 with ExitStack() as stack:520 As shown, :class:`ExitStack` also makes it quite easy to use :keyword:`with`531 method. By using :class:`ExitStack` the steps in the context management534 stack = ExitStack()[all …]
5 from contextlib import ExitStack21 stack = ExitStack()
4 from contextlib import ExitStack289 with ExitStack() as cleanup:
12 from contextlib import ExitStack1339 with ExitStack() as resources:
20 from contextlib import ExitStack1530 self.resources = ExitStack()
920 exit_stack = ExitStack
305 with contextlib.ExitStack() as stack:
1541 with contextlib.ExitStack() as cleanup:
2092 with contextlib.ExitStack() as stack:
4523 with contextlib.ExitStack() as stack:
45 with contextlib.ExitStack() as stack:
454 class ExitStack(_BaseExitStack, AbstractContextManager): class
244 contextlib.ExitStack() and one of the exit stack generators catches and
435 simpler and faster alternative to ExitStack() when handling optional context
1403 contextlib.ExitStack() and one of the exit stack generators catches and
808 with contextlib.ExitStack() as stack:
1145 return contextlib.ExitStack()
1039 :class:`~contextlib.ExitStack` now provides a solid foundation for
824 context manager than :class:`~contextlib.ExitStack`.
2639 - Issue #20317: ExitStack.__exit__ could create a self-referential loop if an3837 - Issue #19092: contextlib.ExitStack now correctly reraises exceptions7357 - Issue #14969: Better handling of exception chaining in contextlib.ExitStack7359 - Issue #14963: Convert contextlib.ExitStack.__exit__ to use an iterative7425 in contextlib.ExitStack (Initial patch by Alon Horev)7554 - Issue #13585: Added contextlib.ExitStack