[New-bugs-announce] [issue4597] EvalFrameEx fails to set 'why' for some exceptions

Jeffrey Yasskin report at bugs.python.org
Mon Dec 8 18:52:13 CET 2008

New submission from Jeffrey Yasskin <jyasskin at gmail.com>:

Several opcodes that can raise an exception fail to set x, err, or why
afterward. This patch fixes all the examples I could find. I could only
figure out how to write a test for PRINT_NEWLINE; the others are hard to

assignee: jyasskin
components: Interpreter Core
files: fix_exceptions.patch
keywords: needs review, patch
messages: 77332
nosy: jyasskin
priority: normal
severity: normal
stage: patch review
status: open
title: EvalFrameEx fails to set 'why' for some exceptions
type: behavior
versions: Python 2.6, Python 2.7, Python 3.0, Python 3.1
Added file: http://bugs.python.org/file12286/fix_exceptions.patch

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list