Message87891
While we seem to disagree on whether this a real bug (and I'll leave it
at that), I'll just stress once again that a "fatal error" is totally
different from an uncontrolled crash like a segmentation fault -- as I
explained and although you don't seem to understand, the "fatal error"
mechanism is there /precisely/ to avoid uncontrolled crashes. Also, your
analogy with processes crashing an X server is flawed. You should be in
control of all the code running in your own program; Python doesn't
offer any mechanism to protect good code from badly written code when
running in the same address space -- any such expectation is misguided.
(for various ways of producing fatal errors, please search for
"Py_FatalError()" in the source tree) |
|
Date |
User |
Action |
Args |
2009-05-16 13:35:57 | pitrou | set | recipients:
+ pitrou, amaury.forgeotdarc, yury |
2009-05-16 13:35:57 | pitrou | set | messageid: <1242480957.57.0.671102470019.issue6028@psf.upfronthosting.co.za> |
2009-05-16 13:35:56 | pitrou | link | issue6028 messages |
2009-05-16 13:35:55 | pitrou | create | |
|