summaryrefslogtreecommitdiff
path: root/Python/pythonrun.c
diff options
context:
space:
mode:
authorAmaury Forgeot d'Arc <amauryfa@gmail.com>2007-11-13 01:05:30 +0000
committerAmaury Forgeot d'Arc <amauryfa@gmail.com>2007-11-13 01:05:30 +0000
commita595a205b889b7122bc5fe74a281dbe97b31e9b7 (patch)
tree9717323ad947de4c9ed33866b7f3b6adc9551a5a /Python/pythonrun.c
parent79ba235bee881e96413fa67c992e4f663baa00d5 (diff)
downloadcpython-a595a205b889b7122bc5fe74a281dbe97b31e9b7.tar.gz
Correction for issue1265 (pdb bug with "with" statement).
When an unfinished generator-iterator is garbage collected, PyEval_EvalFrameEx is called with a GeneratorExit exception set. This leads to funny results if the sys.settrace function itself makes use of generators. A visible effect is that the settrace function is reset to None. Another is that the eventual "finally" block of the generator is not called. It is necessary to save/restore the exception around the call to the trace function. This happens a lot with py3k: isinstance() of an ABCMeta instance runs def __instancecheck__(cls, instance): """Override for isinstance(instance, cls).""" return any(cls.__subclasscheck__(c) for c in {instance.__class__, type(instance)}) which lets an opened generator expression each time it returns True. Seems a backport candidate, even if the case is less frequent in 2.5.
Diffstat (limited to 'Python/pythonrun.c')
0 files changed, 0 insertions, 0 deletions