Rok Mandeljc
Rok Mandeljc
It seems to work as expected on my test Windows 10 system, with python 3.12.0 (32-bit installer from Python.org) and PyInstaller 5.13.2 (since the end of your build log suggests...
Also, does building with PyInstaller v6 make any difference?
> with force `utf8_mode=1` to `app.spec`: Yeah, I just noticed the examples in documentation are wrong - it should be just `utf8` instead of `utf8_mode`: ``` [('X utf8=1', None, 'OPTION')],...
Can you upload your build somewhere so I can try running it in my test environment? This way, we can rule out the differences in build - which will likely...
Also, do you explicitly enable utf8 mode in your python? Do you have `PYTHON*` environment variables set?
> I think it's because of that OS. I tested exact built app on win11-22h2 and works with these flags (no new change): Indeed, it works for me as well....
> So, if issue is with OS, the main quesion is why python interpreter works on it? No idea, really. I'll have to test with 1507, and if I can...
From what I can tell, the behavior difference between python and frozen application comes from the way the bootloader is compiled (which makes sense, because the bootloader itself does not...
Actually, it might be a matter of `ucrt` being linked statically vs. dynamically. Seems we are using the default (static), but python executable is dynamically linked against `ucrt` (that's why...
Yeah, this is going to be a pain one way or another... When building with MSVC, we are not specifying either `/MT` nor `/MD`, so `/MT` (static linking against CRT)...