[issue20317] ExitStack hang if enough nested exceptions

Changes by Nick Coghlan : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___ Pyt

[issue20317] ExitStack hang if enough nested exceptions

Roundup Robot added the comment: New changeset b3eaeb4bdf84 by Nick Coghlan in branch '3.3': Issue 20317: Remove debugging code from contextlib http://hg.python.org/cpython/rev/b3eaeb4bdf84 New changeset a0bf53afedfa by Nick Coghlan in branch 'default': Merge removal of issue 20317 debugging cod

[issue20317] ExitStack hang if enough nested exceptions

Roundup Robot added the comment: New changeset 46c3ea358784 by Nick Coghlan in branch 'default': Merge #20317 from 3.3 http://hg.python.org/cpython/rev/46c3ea358784 -- ___ Python tracker ___

[issue20317] ExitStack hang if enough nested exceptions

Nick Coghlan added the comment: Oh, that's quite neat. Because of the way _GeneratorContextManager works, the context is actually already set correctly on the thrown exceptions, but ExitStack is assuming it will be wrong. This means _fix_exception (part of ExitStack.__exit__) ends up setting t

[issue20317] ExitStack hang if enough nested exceptions

Roundup Robot added the comment: New changeset b3c2472c12a1 by Nick Coghlan in branch '3.3': Issue #20317: Don't create a reference loop in ExitStack http://hg.python.org/cpython/rev/b3c2472c12a1 -- nosy: +python-dev ___ Python tracker

[issue20317] ExitStack hang if enough nested exceptions

Changes by R. David Murray : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue20317] ExitStack hang if enough nested exceptions

New submission from jcflack: Python 3.3.2 (default, Dec 4 2013, 20:19:27) [GCC 4.7.3] on linux (gentoo) Suppose we create a context manager that will fail during exit because of a simple coding error: @contextmanager def f(): try: yield 6 finally: throdbog() # woops, forgot to define t