[CentralOH] wxPython / Py2Exe

Mark Erbaugh mark at microenh.com
Mon Mar 14 20:12:48 CET 2011


I wrote an application several years ago using wxPython and created a Windows (XP) executable with Py2exe.  One of my users got a new computer with Windows 7 Home Premium 64-bit and the application is now crashing. The application starts up with a splash / login screen which she sees. When she tries to log in, the wxPython stdout / stderr output screen briefly flashes (it took her several attempts to get a partial screen capture of this window so I know what it is, but the screen capture doesn't show all the window, especially the part where it tells what the problem  is.

I've seen stdout / stderr window before when a program raises an uncaught exception, but it usually stays on the screen.  Is the fact that it is going away due to the fact that I used Py2exe or is this a Windows 7 thing?  We've tried running the program from the command line and nothing is written to the console window. She's looked in the log files and there doesn't appear to be anything written there, although I'm new to Windows 7 and the errors may be hidden somewhere we haven't looked.

I tried running the program on a clean install of Windows 7 Home Premium (both 64 and 32 bit versions) and it runs fine for me.

There's no installation. The users copy the exe file and a couple of supporting files to their hard drive. For Vista and Windows 7 with UAC, I tell them to copy the folder to the "Documents" folder. Most of the program and supporting libraries  are contained in the executable, but I found I had to distribute MSVCR71.dll and gdipluss.dll with the program to make it run on some machines where those weren't installed. On my clean install of W7 Home Premium 64-bit it looks like those files aren't needed. The program will run without those files in the program's folder.

Any suggestions?

Thanks,
Mark


More information about the CentralOH mailing list