Hi, I'm glad, this problem is gone. Anyway I would have liked to find the reason. Bad luck, so.
Am 23.03.2014 15:30, schrieb Gary Strangman: > I actually used my own Hello World example: > > --------- hello.py -------------- > print "Hi" > ------------------------------------- Is this the same program you used in your first try? If so, I *really* wonder wy the PyQT4 an tkinter hooks have been triggered. > Seems like that shouldn't crash, unless I've got something screwed up. > ;-) I'm not sure if the first ~50 lines will be useful (I get a few > 100) but here they are (followed by the tail): Thanks for including the tail, too. Now as the problem is gone, the DEBUG-log is indeed useless. > So, whatever was wrong somehow got fixed. Thank you ... Well, you are still s > Thinking windoze-like, could I have failed to reboot at the right time > after install or something? Just a random thought Except if Microsoft implemented some magic into Windows,rebooting does not change anything regarding PyInstaller. There is no such thing like an "install" for PyInstaller nor does PyInstaller read any registry entries for its basic work. So sad, you can not reproduce the problem. For the case it reappears, please send me the complete DEBUG output via private mail. -- Schönen Gruß Hartmut Goebel Dipl.-Informatiker (univ), CISSP, CSSLP Information Security Management, Security Governance, Secure Software Development Goebel Consult, Landshut http://www.goebel-consult.de Blog: http://www.goebel-consult.de/blog/quelltext-fur-tolino-shine Kolumne: http://www.cissp-gefluester.de/2012-04-compliance-bringt-keine-sicherheit Goebel Consult ist Mitglied bei http://www.7-it.de/
smime.p7s
Description: S/MIME Cryptographic Signature
