As a followup to this issue - I haven't yet found an explanation for why wxPython 3.0 has problems, but I can confirm that the issue is not present when using wxPython 2.9.5.


On Mon, Jul 28, 2014 at 11:22 AM, Daniel Casper <> wrote:
I've recently updated to the latest wxPython release, 3.0, to gain access to a Utility Class for FontInfo that doesn't require the creation of a wx.App instance.  Seemingly works fine and well, but the new wxPython version doesn't appear to be compatible with bundle_files 2.  bundle_files 3 works as expected, so I'm hoping there's a workaround, or some other way to approach it.

If I'm running my compiled UI with bundle_files 2 with PY2EXE_VERBOSE set, The final lines of my output look like this:

# zipimport: zlib available
# zipimport: zlib available
# found unicodedata.pyd in zipfile j:\RpmV\RPM UI - V2\ui_x86\common.bin
# zipimport: zlib available
import unicodedata # loaded from zipfile j:\RpmV\RPM UI - V2\ui_x86\common.bin\unicodedata.pyd
import stringprep # loaded from Zip j:\RpmV\RPM UI - V2\ui_x86\common.bin\stringprep.pyo
import array # builtin
import encodings.idna # loaded from Zip j:\RpmV\RPM UI - V2\ui_x86\common.bin\encodings\idna.pyo
# zipimport: zlib available
import encodings.ascii # loaded from Zip j:\RpmV\RPM UI - V2\ui_x86\common.bin\encodings\ascii.pyo

And then my application faults.  (Not Terribly Useful) Relevant information from the Windows Event Logs:

Faulting application name: rpmguic.exe, version:, time stamp: 0x52936cf5
Faulting module name: unknown, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x03159602
Faulting process id: 0x16dc
Faulting application start time: 0x01cfaa87c43955db
Faulting application path: j:\RpmV\RPM UI - V2\ui_x86\rpmguic.exe
Faulting module path: unknown
Report Id: 040d6cbd-167b-11e4-8b60-0090f5d3e3ac

I'm intending to test with the latest py2exe as well.  If anything changes in my results I'll follow up.

Thanks in advance for any suggestions,