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 eryksun
Recipients eryksun, ezio.melotti, paul.moore, steve.dower, tim.golden, twoone3, vstinner, zach.ware
Date 2020-10-05.13:26:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1601904414.0.0.233035440835.issue41941@roundup.psfhosted.org>
In-reply-to
Content
> config_init_stdio() is not called in an isolated configuration:

config_init_stdio wasn't being called anyway since Py_Initialize uses _PyConfig_InitCompatConfig. The issue was primarily due to the LC_CTYPE locale being set to the default user locale, as I discussed in msg378024.

Note that for legacy mode, i.e. Py_LegacyWindowsStdioFlag = 1, there's no simple way to not modify the standard I/O files. The io stack needs binary mode. You'd have to use and modify duped file descriptors.
History
Date User Action Args
2020-10-05 13:26:54eryksunsetrecipients: + eryksun, paul.moore, vstinner, tim.golden, ezio.melotti, zach.ware, steve.dower, twoone3
2020-10-05 13:26:54eryksunsetmessageid: <1601904414.0.0.233035440835.issue41941@roundup.psfhosted.org>
2020-10-05 13:26:53eryksunlinkissue41941 messages
2020-10-05 13:26:53eryksuncreate