Hi all. I'm curious if anyone has any pointers on how to solve an issue I see with a PyInstaller created executable in Linux. I have an executable I created using the onefile argument. As the code runs it attempts to use the unicodedata.so object in /tmp/_ME<some random string>; however, that SO does not exist. I do see the module in question present though when I do a pyi-archive_viewer on the executable. As far as I can tell, everything that it needs to import is there.
How does the PyInstaller bootloader attached to the executable determine and keep track of those tmp directory names? I have other directories which were obviously created by the bootloader, and unicodedata.so is in those directories. Likewise, if I delete those /tmp/_ME<blah> directories and rerun the executable - the executable run ok up to a point. It however does NOT create another _ME<blah> directory with the modules in it. I can still run the executable and it seems fine, up to the point that it crashes because of the unicodedata.so issue. Also, I have tried the --noupx argument on the create. That has no observed effect. Thoughts? Any help would be appreciated. BTW, when is the release timeline on the 3.0 version? Thanks, -Dirv -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
