[Py2exe-users] py2exe, wxPython & zipextimporter error

So... continuing this thread, I am still hoping to get some input from "the powers that be" on resolving the core issue...

Here's some more information that I hope will be helpful towards that goal:

1) I don't have any problem building my gui on my home system, which is:

    OS: Windows XP Home (Not sure what SP level)
    Python: 2.4.3
    wx: 2.6.3.3
    py2exe: 0.6.5

    That is, the build runs fine and the executable executes as expected.

2) That same executable runs on my Windows 2000 Pro system without error.

3) A somewhat surprising point (and perhaps good news) is: executables built on Win 2000 Pro (and which error there) will execute under other Windows XP systems we have here in the office without error.

    This would strongly seem to be pointing towards something lacking in our Windows 2000 environment, but the error message certainly doesn't seem to be leading that way (Wk2000 is my app name here):

Traceback (most recent call last):
  File "Wk2000.py", line 3, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\__init__.pyo", line 45, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\_core.pyo", line 4, in ?
  File "zipextimporter.pyo", line 98, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd

Anybody out there seen similar problems? Anybody out there have any idea what sort of fix can be applied to Windows 2000 to resolve the error?

Thanks,
-ej

A couple of things that may really be stupid, but still worth checking.

Are you sure that you've deleted the build and dist (and any other) folders that py2exe creates? Sometimes weird things happen when old versions of modules stick around.

Also, have you tried to explicitly import wx._core? Maybe something goes wrong with py2exe dependency resolution.

ejohnso9@earthlink.net wrote:

···

So... continuing this thread, I am still hoping to get some input from "the powers that be" on resolving the core issue...

Here's some more information that I hope will be helpful towards that goal:

1) I don't have any problem building my gui on my home system, which is:

    OS: Windows XP Home (Not sure what SP level)
    Python: 2.4.3
    wx: 2.6.3.3
    py2exe: 0.6.5

    That is, the build runs fine and the executable executes as expected.

2) That same executable runs on my Windows 2000 Pro system without error.

3) A somewhat surprising point (and perhaps good news) is: executables built on Win 2000 Pro (and which error there) will execute under other Windows XP systems we have here in the office without error.

    This would strongly seem to be pointing towards something lacking in our Windows 2000 environment, but the error message certainly doesn't seem to be leading that way (Wk2000 is my app name here):

Traceback (most recent call last):
  File "Wk2000.py", line 3, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\__init__.pyo", line 45, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\_core.pyo", line 4, in ?
  File "zipextimporter.pyo", line 98, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd

Anybody out there seen similar problems? Anybody out there have any idea what sort of fix can be applied to Windows 2000 to resolve the error?

Thanks,
-ej

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org

There's another thing you might want to try.

I've looked at the C code of py2exe and it seems that the MemoryLoadLibrary function that's causing problems will print some more information about what's happening if you compile it in debug mode (python setup.py build --debug). If you do that and run DebugView (http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx) while you're trying to run your program, you should get debug messages

Let me know if you want to follow this route and need some help. I think it might be a bit of an off-topic for this mailing list.

ejohnso9@earthlink.net wrote:

···

sent by MemoryLoadLibrary via the OutputDebugString Win32 API function.

So... continuing this thread, I am still hoping to get some input from "the powers that be" on resolving the core issue...

Here's some more information that I hope will be helpful towards that goal:

1) I don't have any problem building my gui on my home system, which is:

    OS: Windows XP Home (Not sure what SP level)
    Python: 2.4.3
    wx: 2.6.3.3
    py2exe: 0.6.5

    That is, the build runs fine and the executable executes as expected.

2) That same executable runs on my Windows 2000 Pro system without error.

3) A somewhat surprising point (and perhaps good news) is: executables built on Win 2000 Pro (and which error there) will execute under other Windows XP systems we have here in the office without error.

    This would strongly seem to be pointing towards something lacking in our Windows 2000 environment, but the error message certainly doesn't seem to be leading that way (Wk2000 is my app name here):

Traceback (most recent call last):
  File "Wk2000.py", line 3, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\__init__.pyo", line 45, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\_core.pyo", line 4, in ?
  File "zipextimporter.pyo", line 98, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd

Anybody out there seen similar problems? Anybody out there have any idea what sort of fix can be applied to Windows 2000 to resolve the error?

Thanks,
-ej

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org

If the win2k pro box is using wxPython 2.8 or higher, it's likely a
gdiplus.dll issue (checking earlier posts in the thread, that seems to
be it). Include that dll with the binary and it should work fine.

I'm surprised someone didn't mention it earlier, I was having the same
issue a few months ago, and the first thing that was mentioned was
'gdiplus.dll'.

- Josiah

ejohnso9@earthlink.net wrote:

···

So... continuing this thread, I am still hoping to get some input from "the powers that be" on resolving the core issue...

Here's some more information that I hope will be helpful towards that goal:

1) I don't have any problem building my gui on my home system, which is:

    OS: Windows XP Home (Not sure what SP level)
    Python: 2.4.3
    wx: 2.6.3.3
    py2exe: 0.6.5

    That is, the build runs fine and the executable executes as expected.

2) That same executable runs on my Windows 2000 Pro system without error.

3) A somewhat surprising point (and perhaps good news) is: executables built on Win 2000 Pro (and which error there) will execute under other Windows XP systems we have here in the office without error.

    This would strongly seem to be pointing towards something lacking in our Windows 2000 environment, but the error message certainly doesn't seem to be leading that way (Wk2000 is my app name here):

Traceback (most recent call last):
  File "Wk2000.py", line 3, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\__init__.pyo", line 45, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\_core.pyo", line 4, in ?
  File "zipextimporter.pyo", line 98, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd

Anybody out there seen similar problems? Anybody out there have any idea what sort of fix can be applied to Windows 2000 to resolve the error?

Thanks,
-ej

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org

ejohnso9@earthlink.net schrieb:

So... continuing this thread, I am still hoping to get some input from "the powers that be" on resolving the core issue...

Here's some more information that I hope will be helpful towards that goal:

1) I don't have any problem building my gui on my home system, which is:

    OS: Windows XP Home (Not sure what SP level)
    Python: 2.4.3
    wx: 2.6.3.3
    py2exe: 0.6.5

    That is, the build runs fine and the executable executes as expected.

2) That same executable runs on my Windows 2000 Pro system without error.

3) A somewhat surprising point (and perhaps good news) is: executables built on Win 2000 Pro (and which error there) will execute under other Windows XP systems we have here in the office without error.

    This would strongly seem to be pointing towards something lacking in our Windows 2000 environment, but the error message certainly doesn't seem to be leading that way (Wk2000 is my app name here):

Traceback (most recent call last):
  File "Wk2000.py", line 3, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\__init__.pyo", line 45, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\_core.pyo", line 4, in ?
  File "zipextimporter.pyo", line 98, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd

Anybody out there seen similar problems? Anybody out there have any idea what sort of fix can be applied to Windows 2000 to resolve the error?

I *will* get back to this problem; however not at the moment - too much on my plate currently ;-).
And at least it should be noted that the error reporting in MemoryLoadLibrary should be improved
so that it is possible to spot the problem.

Thomas

ejohnso9@earthlink.net schrieb:

So... continuing this thread, I am still hoping to get some input from "the powers that be" on resolving the core issue...

Here's some more information that I hope will be helpful towards that goal:

1) I don't have any problem building my gui on my home system, which is:

    OS: Windows XP Home (Not sure what SP level)
    Python: 2.4.3
    wx: 2.6.3.3
    py2exe: 0.6.5

    That is, the build runs fine and the executable executes as expected.

2) That same executable runs on my Windows 2000 Pro system without error.

3) A somewhat surprising point (and perhaps good news) is: executables built on Win 2000 Pro (and which error there) will execute under other Windows XP systems we have here in the office without error.

    This would strongly seem to be pointing towards something lacking in our Windows 2000 environment, but the error message certainly doesn't seem to be leading that way (Wk2000 is my app name here):

Traceback (most recent call last):
  File "Wk2000.py", line 3, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\__init__.pyo", line 45, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\_core.pyo", line 4, in ?
  File "zipextimporter.pyo", line 98, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd

... and it should be clear that you can avoid this problem by
*not* building a single-file executable. Maybe this even
allows to find the reason for this error.

Thomas

Traceback (most recent call last):
  File "Wk2000.py", line 3, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\__init__.pyo", line 45, in ?
  File "zipextimporter.pyo", line 82, in load_module
  File "wx\_core.pyo", line 4, in ?
  File "zipextimporter.pyo", line 98, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd

Anybody out there seen similar problems? Anybody out there have any idea what sort of fix can be applied to Windows 2000 to resolve the error?

If the win2k pro box is using wxPython 2.8 or higher, it's likely a
gdiplus.dll issue (checking earlier posts in the thread, that seems to
be it). Include that dll with the binary and it should work fine.

I'm surprised someone didn't mention it earlier, I was having the same
issue a few months ago, and the first thing that was mentioned was
'gdiplus.dll'.

It would be *great* if some more or even less experienced people
would step up again to answer these questions, and hopefully even
continue to submit useful information into the py2exe wiki.

Is there anything that should be done to make this happen?

Neither Jimmy nor me have enough time available to do all this
support (but for whom isn't that the case also ;-).

Thanks,
Thomas