Hi folks. I create a small wxPython program which I then run.
When I logout from Windows, the program exits cleanly as wxPython allows me to catch the Windows logout event and perform cleanup. However, if I then freeze the program with pyInstaller --onefile, the resulting .EXE, when run, doesn't exit cleanly on logout, and leaves a _MEIXXXX folder around. Investigating further, I can see that running the .EXE causes two processes to run. The first, I'm guessing, performs some kind of bootstrapping, unpacking to a temporary folder and running the second, larger process. If I send the logout event to the larger of the processes, it exits cleanly, and the smaller process then exits after cleaning up the temporary folder. However, if I send the event to the smaller process, it immediately ignores it. (There is a windows program called called rmtool which allows me to send the logout event to a set of processes to see how they handle it without actually logging out.) Is there something I can set in the spec file to allow the bootstrap process to handle the logout event cleanly? Thanks! -- gyre -- -- 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.
