A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-November/039938.html below:

[Python-Dev] XXX undetected error (why=3)

[Python-Dev] XXX undetected error (why=3) [Python-Dev] XXX undetected error (why=3)Jeremy Hylton jeremy at alum.mit.edu
Tue Nov 4 01:10:12 EST 2003
I've been seeing these problems sporadically over the last several
months.  Fred and I tracked one of them down to a bug in pyexpat.c.  I
noticed several more running the Zope 3 test suite today.

I'd like to change the code for the check to call Py_FatalError()
instead of printing a message to stderr.  The check is only enabled
during a debug build.  I'd be much happier debugging this from a core
dump than trying to figure out what happened to cause the message to be
printed.

Any objections?

Jeremy



More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4