Message 305583 - Python tracker

➜

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.

In-reply-to
Author	ncoghlan
Recipients	Arfrever, Drekin, Gregory.Salvan, barry, dstufft, eric.snow, jcea, ncoghlan, sbspider, serhiy.storchaka, terry.reedy, twouters, vstinner
Date	2017年11月05日.04:37:08
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1509856629.8.0.213398074469.issue22257@psf.upfronthosting.co.za>

Content
Bug report (since resolved) that highlighted our general lack of test coverage for the interactions between environment variable based configuration and command line based configuration: https://bugs.python.org/issue31845 This work revealed the absence, since the refactoring changes the order in which we check environment variables and the command line (we used to check the command line first, and then env vars later during Py_Initialize, now we check env vars in _Py_InitializeCore, and the command line afterwards). Something I'd also forgotten is that I'd switched the PEP to use "_Py_InitializeRuntime" and "_Py_ConfigureMainInterpreter", but the draft implementation is currently still using "_Py_InitializeCore" and "_Py_InitializeMainInterpreter". For that last point, it's probably easier to change the PEP back than it is to tinker with the implementation - those specific API names are pretty arbitrary anyway.

Content

Bug report (since resolved) that highlighted our general lack of test coverage for the interactions between environment variable based configuration and command line based configuration: https://bugs.python.org/issue31845
This work revealed the absence, since the refactoring changes the order in which we check environment variables and the command line (we used to check the command line first, and then env vars later during Py_Initialize, now we check env vars in _Py_InitializeCore, and the command line afterwards).
Something I'd also forgotten is that I'd switched the PEP to use "_Py_InitializeRuntime" and "_Py_ConfigureMainInterpreter", but the draft implementation is currently still using "_Py_InitializeCore" and "_Py_InitializeMainInterpreter".
For that last point, it's probably easier to change the PEP back than it is to tinker with the implementation - those specific API names are pretty arbitrary anyway.

History
Date	User	Action	Args
2017年11月05日 04:37:10	ncoghlan	set	recipients: + ncoghlan, twouters, barry, terry.reedy, jcea, vstinner, Arfrever, eric.snow, serhiy.storchaka, Drekin, dstufft, Gregory.Salvan, sbspider
2017年11月05日 04:37:09	ncoghlan	set	messageid: <1509856629.8.0.213398074469.issue22257@psf.upfronthosting.co.za>
2017年11月05日 04:37:09	ncoghlan	link	issue22257 messages
2017年11月05日 04:37:08	ncoghlan	create

homepage