summaryrefslogtreecommitdiffstats
path: root/Misc
diff options
context:
space:
mode:
authorAmaury Forgeot d'Arc <amauryfa@gmail.com>2007-11-13 01:05:30 (GMT)
committerAmaury Forgeot d'Arc <amauryfa@gmail.com>2007-11-13 01:05:30 (GMT)
commitf05149a257560144cbaaea3e96c404803dbf26e4 (patch)
treec2f858ed25b8db3a0f90905fbc4c7b5e4089e9f1 /Misc
parent8161a65cd865b6be4d1269791ff7c71c158c699b (diff)
downloadcpython-f05149a257560144cbaaea3e96c404803dbf26e4.zip
cpython-f05149a257560144cbaaea3e96c404803dbf26e4.tar.gz
cpython-f05149a257560144cbaaea3e96c404803dbf26e4.tar.bz2
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 'Misc')
0 files changed, 0 insertions, 0 deletions