23 Oct
2012
23 Oct
'12
12:04 a.m.
Stephen J. Turnbull wrote:
For most users, it doesn't matter whether an environment variable is set incorrectly without their knowledge, or if the kernel is buggy, or if the disk is corrupt. And from Python's point of view, the world as a whole no longer makes.
So it shuts down abnormally. That's what an abort means, in programming as in rocket launches.
Seems to me the only reason to use SIGABRT rather than exit() with an error code is to provoke a core dump, and that's only useful if we suspect a bug in Python itself. That's not the case here -- the cause is clearly something external. -- Greg