[issue4597] EvalFrameEx fails to set 'why' for some exceptions

[Jeffrey Yasskin]

New submission from Jeffrey Yasskin <[EMAIL PROTECTED]>:

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
trigger.

--
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 <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4597] EvalFrameEx fails to set 'why' for some exceptions

[Neal Norwitz]

Neal Norwitz <[EMAIL PROTECTED]> added the comment:

The patch looks good.

These problems also apply to 2.5 I assume?  You might want to ping MvL
to let him know since he's about to cut that release.

--
keywords:  -needs review
nosy: +nnorwitz

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4597] EvalFrameEx fails to set 'why' for some exceptions

[Jeffrey Yasskin]

Jeffrey Yasskin <[EMAIL PROTECTED]> added the comment:

Submitted as r67666. I'll ping Martin.

--
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4597] EvalFrameEx fails to set 'why' for some exceptions

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

This is fine to port to 2.5; please go ahead. Don't forget to add
Misc/NEWS entries, though - also add them for the branches you have
changed already.

--
nosy: +loewis

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4597] EvalFrameEx fails to set 'why' for some exceptions

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Reopening: this need to be manually merged into 2.6 and 3.0 maintenance 
branches.

+ a NEWS entry is still missing.

--
nosy: +amaury.forgeotdarc
stage: committed/rejected -> commit review
status: closed -> open

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4597] EvalFrameEx fails to set 'why' for some exceptions

[Jeffrey Yasskin]

Jeffrey Yasskin <[EMAIL PROTECTED]> added the comment:

Added NEWS in r67685; ported to 2.5 branch in r67687; to 2.6 branch in
r67696; to 3.1 branch in r67697; and to 3.0 branch in r67698.

--
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com