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 barry
Recipients barry, brett.cannon, christian.heimes, gvanrossum, lukasz.langa, methane, rhettinger, serhiy.storchaka, terry.reedy, vstinner
Date 2017-11-03.20:38:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <2670D8E0-49E7-4BAE-8D88-42C126A3E0E9@python.org>
In-reply-to <1509732303.61.0.213398074469.issue31415@psf.upfronthosting.co.za>
Content
On Nov 3, 2017, at 11:05, Serhiy Storchaka <report@bugs.python.org> wrote:
> 
> But now, after adding the environment variable, do we still need the -X option? From a user side I don't see much difference between specifying an option and an environment variable, but the code for handling the environment variable is much simpler.

It’s a good question.  I guess in the limited amount of time I’ve used the feature so far, I find it kind of nice to be able to type `python -X importtime` when doing general import profiling.  The use case for the environment variable is more compelling IMHO which is why I really wanted to add it.  I suppose typing `PYTHONPROFILEIMPORTTIME=x python` isn’t *too* onerous, even if it is kind of a weird long mashed together word.

I suppose I’m -0 on removing the -X option, and +0 on adding the negative cache.
History
Date User Action Args
2017-11-03 20:38:15barrysetrecipients: + barry, gvanrossum, brett.cannon, rhettinger, terry.reedy, vstinner, christian.heimes, methane, lukasz.langa, serhiy.storchaka
2017-11-03 20:38:15barrylinkissue31415 messages
2017-11-03 20:38:15barrycreate