[issue34639] PYTHONCOERCECLOCALE is ignored when using -E or -I option

STINNER Victor added the comment: The discussion moved back to bpo-34589. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Py_Initialize() and Py_Main() should not enable C locale coercion ___ Python tracker

[issue34639] PYTHONCOERCECLOCALE is ignored when using -E or -I option

STINNER Victor added the comment: > Respecting -E and -I isn't a problem per se - the problem is moving the > _Py_CoerceLegacyLocale call to a point that's incredibly late in the startup > process *just* to get it to respect those flags. Would you mind to elaborate how it is an issue? The

[issue34639] PYTHONCOERCECLOCALE is ignored when using -E or -I option

Nick Coghlan added the comment: For the PYTHONCOERCECLOCALE=warn case, it turns out that my preferred approach to implementing bpo-34589 also naturally ends up respecting -I and -E for that (i.e. supplying -I or -E will suppressed the warning). However, my upcoming PR for that also

[issue34639] PYTHONCOERCECLOCALE is ignored when using -E or -I option

Nick Coghlan added the comment: Respecting -E and -I isn't a problem per se - the problem is moving the _Py_CoerceLegacyLocale call to a point that's incredibly late in the startup process *just* to get it to respect those flags. I don't actually mind if you reinstate the extra pass through

[issue34639] PYTHONCOERCECLOCALE is ignored when using -E or -I option

Change by STINNER Victor : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34639] PYTHONCOERCECLOCALE is ignored when using -E or -I option

New submission from STINNER Victor : I modified Py_Main() to ignore the PYTHONCOERCECLOCALE environment variable if -E or -I command line option is used. But Nick asks to always read PYTHONCOERCECLOCALE. We should either update the PEP or change the code. I am not sure why