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 vstinner
Recipients bstorm, eryksun, ned.deily, paul.moore, steve.dower, tim.golden, vinay.sajip, vstinner, zach.ware
Date 2019-06-27.23:29:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561678155.36.0.340379291611.issue37369@roundup.psfhosted.org>
In-reply-to
Content
> For 3.8 I can apply the same fix and make sys.base_executable public, or keep it as sys._base_executable. Either way, it'll show up in PyConfig. (Victor - thoughts here? Should be a non-breaking change, right?)

There is _PyConfig._config_version which is designed to support PyConfig change without losing ABI compatibility... but I didn't implement code for that yet :-)

If you have to modify PyConfig in 3.8, I suggest to directly use "base_executable" "public" name there (don't change it from _base_executable  to base_executable from 3.8 to 3.9, it would be painful).

I'm not sure of the purpose of sys._base_executable. Maybe open a separated issue to make the attribute public? I'm not sure if multiprocessing (for example) should use it, or if sys.executble should be used.
History
Date User Action Args
2019-06-27 23:29:15vstinnersetrecipients: + vstinner, paul.moore, vinay.sajip, tim.golden, ned.deily, zach.ware, eryksun, steve.dower, bstorm
2019-06-27 23:29:15vstinnersetmessageid: <1561678155.36.0.340379291611.issue37369@roundup.psfhosted.org>
2019-06-27 23:29:15vstinnerlinkissue37369 messages
2019-06-27 23:29:15vstinnercreate