[Python-Dev] Idea for avoiding exception masking (original) (raw)
Greg Ewing greg@cosc.canterbury.ac.nz
Thu, 30 Jan 2003 09:53:01 +1300 (NZDT)
- Previous message: [Python-Dev] Idea for avoiding exception masking
- Next message: [Python-Dev] Idea for avoiding exception masking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
So what would exception chaining mean for the C API?
PyErrSetString(PyExcTypeError, "wrong type"); PyErrSetString(PyExcTypeError, "can't iterate"); The second call would normalize the first exception and attach it to the second as the cause attribute? But then the second exception would have to be normalized too.
To maintain delayed normalisation, there would have to be a fourth global variable holding the current "cause" (a normalised exception or None).
Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg@cosc.canterbury.ac.nz +--------------------------------------+
- Previous message: [Python-Dev] Idea for avoiding exception masking
- Next message: [Python-Dev] Idea for avoiding exception masking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]