This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients amaury.forgeotdarc, belopolsky, davidfraser, dmalcolm, joshbressers, pitrou, scott.dial, sjt, vstinner
Date 2010-12-23.02:45:47
SpamBayes Score 2.16493e-15
Marked as misclassified No
Message-id <>
In-reply-to <>
On Wed, Dec 22, 2010 at 9:27 PM, Scott Dial <> wrote:
> Scott Dial <> added the comment:
> On 12/22/2010 8:52 PM, STINNER Victor wrote:
> > Amaury asked for a sys.setsegfaultenabled() option: I think that the command line option and the environment variable are enough.
> I really think you should think of it as a choice the developer of an
> application makes instead of a choice an application user makes. A
> setsegfaultenabled() could just be another step of initializing the
> application akin to setting up the logging module, for instance. In that
> situation, a function call has a much lower barrier for use than a CLI
> option or environment variable where you'd have to create a wrapper script.


I would actually prefer just sys.setsegfaultenabled() without a
controlling environment variable.  If necessary, the environment
variable can be checked in and sys.setsegfaultenabled()

As I suggested on python-dev, I also think this belongs to a separate
module rather than core or sys.  The relevant code is already
segregated in a file, so turning it into a module should not be
difficult.  The only function that probably must stay in core is
_Py_DumpBacktrace().  With say "segvhandler" module, can
include something like this:

if sys.getenv('PYTHONSEGVHANDLER'):
     import segvhandler

Does the latest patch address the GIL/multithreading issues?
Date User Action Args
2010-12-23 02:45:48belopolskysetrecipients: + belopolsky, amaury.forgeotdarc, davidfraser, scott.dial, pitrou, vstinner, sjt, dmalcolm, joshbressers
2010-12-23 02:45:47belopolskylinkissue8863 messages
2010-12-23 02:45:47belopolskycreate