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

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

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

• Previous message: [Python-Dev] XXX undetected error (why=3)
• Next message: [Python-Dev] test warnings for "%x"%id(foo) on 2.3 branch
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[Jeremy Hylton]
> ...
> 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?

+1.  Having catastrophic errors fly by on stderr isn't a good idea even
without the (strong) debuggability argument.

• Previous message: [Python-Dev] XXX undetected error (why=3)
• Next message: [Python-Dev] test warnings for "%x"%id(foo) on 2.3 branch
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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