[PyInstaller] 3.2 Regression

[Coyot Linden (Glenn Glazer)]

Hi, folks. We are using pyinstaller in our CMake file like this (I've replaced the executable name with <EXE> for NDA reasons):     add_custom_command(     OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/<EXE>     COMMAND ${PYTHON_DIRECTORY}/Scripts/pyinstaller.exe     ARGS        --onefile        --log-level WARN        --distpath ${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}             ${CMAKE_SOURCE_DIR}/<more path>/<EXE>     COMMENT "Performing pyinstaller compile of <EXE>" and in my local Windows box running PyInstaller 3.1.1. everything works fine. However, when we built the code on Teamcity, we got the following sort of error: [21:37:54][LogScan] 21> File "C:\Python27\lib\site-packages\PyInstaller\building\utils.py", line 521, in _load_code [21:37:54][LogScan] 21> assert loader and hasattr(loader, 'get_code') [21:37:54][LogScan] 21> AssertionError [21:37:54][LogScan] 21>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5): error MSB6006: "cmd.exe" exited with code 1. On some investigation, we discovered that the Teamcity host had picked up 3.2 from pip since it was run some time after pip was run locally.  Performing: pip install 'pyinstaller==3.1.1' --force-reinstall on the Teamcity host caused it to build fine again, so I feel there is a regression in 3.2.  I see from some googling that there have been other problems with this assert, though perhaps of different etiology, such as unicode issues. Is this a known bug?  I don't see an issue quite like it in github. Best, coyot -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to pyinstaller+unsubscr...@googlegroups.com. To post to this group, send email to pyinstaller@googlegroups.com. Visit this group at https://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.