Antoine Pitrou <[EMAIL PROTECTED]> added the comment: With or without my patch, bare "raise" inside a "finally" statement raises a "RuntimeError: no active exception to re-raise". (except, of course, when the try/finally is itself enclosed in an except block) That's because a finally block is not considered an exception handler. I don't think there's any reason to change this.
I'm not for adding syntax errors. After all the bare "raise" statement just does the moral equivalent of re-raising sys.exc_info() verbatim. In those situations where sys.exc_info() would return a non-empty result, why shouldn't "raise" be accepted as well? _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3021> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
