Hi, Josiah Carlson <[EMAIL PROTECTED]> wrote in news:[EMAIL PROTECTED]:
> In looking at the use of Py_FatalError in the Python Sources (it's a 10 > meg tarball that is well worth the download), it looks as though its use > shows a Fatal error (hence the name). Things like "Inconsistant > interned string state" or "Immortal interned string died" or "Can't > initialize type", etc. > > Essentially, those errors generally signify "the internal state of > python is messed up", whether that be by C extension, or even a bug in > Python. The crucial observation is that many of them have ambiguous > possible recoveries. How do you come back from "Can't initialize type", > or even 'gc couldn't allocate "__del__"'? The hook is not to come back just for logging, see my previous post please. Best regards. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
