Author pitrou
Recipients amaury.forgeotdarc, pitrou, yury
Date 2009-05-16.13:35:55
SpamBayes Score 2.79231e-09
Marked as misclassified No
Message-id <1242480957.57.0.671102470019.issue6028@psf.upfronthosting.co.za>
In-reply-to
Content
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)
History
Date User Action Args
2009-05-16 13:35:57pitrousetrecipients: + pitrou, amaury.forgeotdarc, yury
2009-05-16 13:35:57pitrousetmessageid: <1242480957.57.0.671102470019.issue6028@psf.upfronthosting.co.za>
2009-05-16 13:35:56pitroulinkissue6028 messages
2009-05-16 13:35:55pitroucreate