Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Analysis: the primary recursion error is correctly raised, but then there is a call to PyErr_NormalizeException, which calls PyEval_CallObject, which increases the stack depth and hit the recursion limit again... python2.5 don't have the problem because PyEval_CallObject did not check the recursion limit.
Different solutions I can think of: - use a prebuilt exception: not possible if we still want an error message containing the context. - in PyErr_NormalizeException, "PyEval_CallObject" is too generic. We could have a special path for exception types deriving from BaseException: directly call the constructor. ---------- nosy: +amaury.forgeotdarc __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2548> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
