Operating system: Windows 10
wxPython version & source: 4.1.1
Python version & source: 3.7.4
I am not sure whether you consider this a bug, but the recent change to InitLocale broke our application. We develop a big application where we load python in-process and there in turn use wxPython.
Our application never changes the locale and expects/requires it to remain set to the "C" locale. After the upgrade to wxPython to 4.1.1 we got strange behavior on non-English systems that we managed to trace back to wxPython changing the process locale.
Would it be possible to go back to a solution closer to what was implemented in 4.1.0, which managed without a setlocale call?
The behavior improved a bit for us with 040c59fd991cd08174b5acee7de9418c23c9de33, but it would still be great to have an option to disable this completely.
Operating system: Windows 10 wxPython version & source: 4.1.1 Python version & source: 3.7.4
I am not sure whether you consider this a bug, but the recent change to
InitLocale
broke our application. We develop a big application where we load python in-process and there in turn use wxPython.Our application never changes the locale and expects/requires it to remain set to the "C" locale. After the upgrade to wxPython to 4.1.1 we got strange behavior on non-English systems that we managed to trace back to wxPython changing the process locale.
Would it be possible to go back to a solution closer to what was implemented in 4.1.0, which managed without a
setlocale
call?