[issue2341] Raise a Py3K warning when raise non-BaseException exceptions

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Checked in as r61486. I tweaked your change slightly to compare the output of PyErr_Warn() with -1. The "minor" patch is incorrect IMO; the code where the comment was originally is indeed normalizing the exception in a specific way, while

[issue2341] Raise a Py3K warning when raise non-BaseException exceptions

Guido van Rossum <[EMAIL PROTECTED]> added the comment: I'll review this soon. -- assignee: -> gvanrossum nosy: +gvanrossum priority: critical -> release blocker __ Tracker <[EMAIL PROTECTED]> __

[issue2341] Raise a Py3K warning when raise non-BaseException exceptions

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: While writing the patch, I noticed that "/* Normalize to raise , */" comment was misplaced. Please consider a minor patch that fixes that. Added file: http://bugs.python.org/file9700/issue2341-minor.diff _

[issue2341] Raise a Py3K warning when raise non-BaseException exceptions

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: See attached. I don't know how to write unit tests for -3 warnings. -- keywords: +patch nosy: +belopolsky Added file: http://bugs.python.org/file9699/issue2341.diff __ Tracker <[EMAIL PROTECTED]

[issue2341] Raise a Py3K warning when raise non-BaseException exceptions

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- priority: immediate -> urgent __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing lis

[issue2341] Raise a Py3K warning when raise non-BaseException exceptions

New submission from Brett Cannon <[EMAIL PROTECTED]>: Raising exceptions that do not inherit from BaseException (e.g., classic classes) should raise a Py3K warning. -- components: Interpreter Core keywords: 26backport messages: 63700 nosy: brett.cannon priority: immediate severity: norma