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 mathias
Recipients eric.snow, mathias, ncoghlan, ronaldoussoren, vstinner
Date 2019-09-26.10:11:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

msg191944 from Nick Coghlan, made me think that with all the initialization rework that appeared to be underway you want to incorporate that presented idea of basing the default onto the location of the or the pythonX.X.dll instead of the location of python/python.exe.
And as mentioned by Ronald Oussoren that would even align the methods used across the architectures to something common with a fallback to the current way that takes the path of the interpreter executable.
At least that is what the provided patch implemented in the old code structure.

And this does not even change the default for the common case where the default is plain useful. It is just changing the way how the default is determined so that the default for the case of an embedded interpreter is more meaningful.

As stated somewhere above. The you can do that with application code when setting up the embedded interpreter, but it would be nice if that just works out of the box and by that helps applications not thinking of that solution.


Date User Action Args
2019-09-26 10:11:35mathiassetrecipients: + mathias, ronaldoussoren, ncoghlan, vstinner, eric.snow
2019-09-26 10:11:35mathiassetmessageid: <>
2019-09-26 10:11:35mathiaslinkissue18309 messages
2019-09-26 10:11:35mathiascreate