[Python-Dev] Raise OSError or RuntimeError in the OS module? (original) (raw)
Georg Brandl g.brandl at gmx.net
Tue May 3 20:30:22 CEST 2011
- Previous message: [Python-Dev] Raise OSError or RuntimeError in the OS module?
- Next message: [Python-Dev] Socket servers in the test suite
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 02.05.2011 12:06, Victor Stinner wrote:
Hi,
I introduced recently the signal.pthreadsigmask() function (issue #8407). pthreadsigmask() (the C function) returns an error code using errno codes. I choosed to raise a RuntimeError using this error code, but I am not sure that RuntimeError is the best choice. It is more an OS error than a runtime error: should signal.pthreadsigmask() raise an OSError instead? signal.signal() raises a RuntimeError if setting the signal handler failed. signal.siginterrupt() raises also a RuntimeError on error. signal.setitimer() and signal.getitimer() have their own exception class: signal.ItimerError, raised on setimer() and getitimer() error.
If it has an errno, it should be a subclass of EnvironmentError.
Georg
- Previous message: [Python-Dev] Raise OSError or RuntimeError in the OS module?
- Next message: [Python-Dev] Socket servers in the test suite
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]