June 10, 2003
12:22 a.m.
I don't have a use case that breaks with this requirement (since you can always use multiple inheritance to make a desirable class raisable).
What if the desirable class has a C layout that conflicts with that of Exception?
Perhaps Exception should have a null C layout? But I still call YAGNI on this use case until I hear a good reason why you'd ever want to raise a 3rd party class and it's not (a) for backwards compatibility reasons or (b) just as easy to raise another class with this class instance as an attribute. --Guido van Rossum (home page: http://www.python.org/~guido/)