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 pitrou
Recipients barry, brett.cannon, christian.heimes, gvanrossum, lukasz.langa, methane, pitrou, rhettinger, serhiy.storchaka, terry.reedy, vstinner
Date 2017-11-04.13:17:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1509801451.17.0.213398074469.issue31415@psf.upfronthosting.co.za>
In-reply-to
Content
One benefit (or drawback, depending on how you see it) of the -X option is that it wouldn't propagate to child processes spawned by multiprocessing.  See _args_from_interpreter_flags() in Lib/subprocess.py.

More generally, the idea that we should remove a command line option because there's an environment variable sounds dubious to me.  Should we do the same for all command-line options?  The faulthandler module can be enabled either using the `PYTHONFAULTHANDLER` environment variable or by specifying `-X faulthandler` on the command line.

The only serious reason I can imagine would be that the -X option has a significant maintenance cost.
History
Date User Action Args
2017-11-04 13:17:31pitrousetrecipients: + pitrou, gvanrossum, barry, brett.cannon, rhettinger, terry.reedy, vstinner, christian.heimes, methane, lukasz.langa, serhiy.storchaka
2017-11-04 13:17:31pitrousetmessageid: <1509801451.17.0.213398074469.issue31415@psf.upfronthosting.co.za>
2017-11-04 13:17:31pitroulinkissue31415 messages
2017-11-04 13:17:31pitroucreate