Movatterモバイル変換

[Python-Dev] Chained Exceptions

• Previous message:[Python-Dev] Tidier Exceptions
• Next message:[Python-Dev] Chained Exceptions
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Suppose exceptions have an optional "context" attribute, which isset when the exception is raised in the context of handling anotherexception.  Thus:    def a():        try:            raise AError        except:            raise BErroryields an exception which is an instance of BError.  This instancewould have as its "context" attribute an instance of AError.Or, in a more complex case:    def compute():        try:            1/0        except Exception, exc:            log(exc)    def log(exc):        try:            file = open('error.log')   # oops, forgot 'w'            print >>file, exc            file.close()        except:            display(exc)    def display(exc):        print 'Aaaack!', ex            # oops, misspelled 'exc'Today, this just gives you a NameError about 'ex'.With the suggested change, you would still get a NameError about 'ex';its 'context' attribute would show that it occurred while handling anIOError on error.log; and this IOError would have a 'context' attributecontaining the original ZeroDivisionError that started it all.What do you think?-- ?!ng

• Previous message:[Python-Dev] Tidier Exceptions
• Next message:[Python-Dev] Chained Exceptions
• Messages sorted by:[ date ][ thread ][ subject ][ author ]