➜

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 scott.dial
Recipients amaury.forgeotdarc, belopolsky, davidfraser, dmalcolm, joshbressers, pitrou, scott.dial, sjt, vstinner
Date 2010-12-23.02:27:00
SpamBayes Score 4.5040275e-07
Marked as misclassified No
Message-id <4D12B36E.6000309@scottdial.com>
In-reply-to <1293069141.78.0.0338938839056.issue8863@psf.upfronthosting.co.za>
Content 
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.
History
Date User Action Args
2010-12-23 02:27:03scott.dialsetrecipients: + scott.dial, amaury.forgeotdarc, davidfraser, belopolsky, pitrou, vstinner, sjt, dmalcolm, joshbressers
2010-12-23 02:27:00scott.diallinkissue8863 messages
2010-12-23 02:27:00scott.dialcreate