Issue 4597: EvalFrameEx fails to set 'why' for some exceptions (original) (raw)

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/48847

classification

process

Created on 2008-12-08 17:52 by jyasskin, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (6)
msg77332 - (view)	Author: Jeffrey Yasskin (jyasskin) *	Date: 2008-12-08 17:52
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.
msg77334 - (view)	Author: Neal Norwitz (nnorwitz) *	Date: 2008-12-08 18:14
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.
msg77335 - (view)	Author: Jeffrey Yasskin (jyasskin) *	Date: 2008-12-08 18:56
Submitted as r67666. I'll ping Martin.
msg77358 - (view)	Author: Martin v. Löwis (loewis) *	Date: 2008-12-08 22:58
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.
msg77576 - (view)	Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) *	Date: 2008-12-10 23:06
Reopening: this need to be manually merged into 2.6 and 3.0 maintenance branches. + a NEWS entry is still missing.
msg77593 - (view)	Author: Jeffrey Yasskin (jyasskin) *	Date: 2008-12-11 06:39
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.