j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
Just van Rossum wrote:
Greg Ewing wrote:
Barry Warsaw wrote:
One possible approach is to revert BaseException out of Py2.5, re-position KeyboardInterrupt, and add Error as an alias for StandardError. Then we can encourage people to start using Error as the base classes for their own errors. Also maybe start issuing warnings whenever you inherit directly from Exception.
Ugh. I hate it when it's made (virtually) impossible to write code that runs warnings-free on both Python X.Y and X.(Y+1).
This was one of the key things that led to the approach in PEP 352. Barry's hierarchy is very similar to some of the suggestions made during the PEP 348 discussion, and they were rejected because they made the transition a hell of a lot harder without any concomitant benefit. I know this because I was one of the people making those suggestions.
With PEP 352 (tweaked to move GeneratorExit out from under Exception):
With Barry's proposed hierarchy:
The additional pain required in order to have 'Exception' at the root of the hierarchy just isn't worth it.