At 02:36 PM 3/24/2006 -0800, Guido van Rossum wrote: >I think it's overkill to warn for any string exceptions thrown this >way. Since the only use case for using throw() is to pass an exception >you just caught, I don't see that putting the warning is useful -- >it's just more code that in practice is never triggered.
My proposal was that throw() should only succeed or fail, never warn. If you throw() a string exception with a traceback, it Just Works. If you throw() a string exception without a traceback, you get an immediate TypeError, just like in the 2.5 trunk now. Is that acceptable? i.e., was that what you were "-0"-ing? The only change is that throw() would now *accept* string exceptions without warning or error, if and only if you supply a traceback. That is, if you are effectively re-raising an existing exception. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
