RetroSearch Browse

Sat Dec 18 17:50:38 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-December/106869.html

Am 18.12.2010 14:57, schrieb Victor Stinner:
> Le 18/12/2010 13:21, Georg Brandl a écrit :
>> I very much like having a traceback on (some) segmentation faults,
> Why do you say "some" segmentation faults?
>> but it's clear there needs to be a way to turn it off.  An environment variable
>> seems to be the obvious choice (for the reasons you stated for
>> PYTHONDONTWRITEBYTECODE).
> Amaury proposed a new function sys.setsegfaultenabled(). Such function 
> can be used in a customized site module. I think that I will implement 
> it in my next patch, before commiting the new feature. I suppose that we 
> also need a function to get the status of the fault handler.
> 
> I just don't like the name. I would prefer sys.setfaulthandlerenabled(), 
> I maybe just sys.setfaulthandler(). As this feature is specific to 
> CPython, should it be protected function? So:
>   * sys._setfaulthandler(bool): enable/disable the fault handler
>   * sys._getfaulthandler()->bool: get the status (enabled/disabled) of 
> the fault handler

In any case, this is coming pretty late; beta 2 is scheduled for this
weekend, and even if this is something that only kicks in when all hope
is lost anyway, it is a new feature.  I should like to hear approval
from a few more devs before I will let this go into 3.2.

Georg

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

Showing content from https://mail.python.org/pipermail/python-dev/2010-December/106869.html below:

[Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER environment variable