1515163 is a regression from 2.4. It is fairly obscure, as it should only affect deprecated string exceptions which also have a value. raise "string", "string" On the other hand, I did run into it while trying to clean up unittest. The patch fixes this problem, and adds several test cases. -jJ
Logged In: YES user_id=764593 In order to fix it, I also broke out some repeated code into a subfunction, and switched some logic to a more modern idiom -- these parts *could* be separated if need be, but I won't be able to do it this week.
Logged In: YES user_id=764593 I forgot to mention in this tracker that this is a regression against 2.4, so it should be fixed even post- beta, unless we decide to never fix it as part of deprecation.
Logged In: YES user_id=764593 traceback.py.diff3.txt is the minimal fix. traceback.py.diff2.txt is a better fix. test_traceback.py.diff.txt strengthens the test cases (not just this bug; a few others tests as well.)