On Mon, May 2, 2016 at 5:17 PM, Random832 <random832@fastmail.com> wrote:
On Mon, May 2, 2016, at 11:14, Guido van Rossum wrote:
On Mon, May 2, 2016 at 8:01 AM, Ryan Gonzalez <rymg19@gmail.com> wrote:
Other than the fact that this would completely fail when run with -O...
But maybe that's fine, or intended.
I can see a fair number of uses for this, including subclasses of AssertionError.
I think this would be an attractive nuisance, and if it's implemented at all it should forbid types that are *not* subclasses of AssertionError in order to mitigate that.
Why such a constraint? I think most of the times the desired exception would be either ValueError or TypeError, both of which do not inherit from AssertionError. -- Giampaolo - http://grodola.blogspot.com