On 6/20/12 4:00 PM, mmiscavage wrote:
I am having a similar problem so I'm posting it here instead of
starting a new thread.
Using the newest download (pyinstaller-pyinstaller-2145d84.zip),
Windows 7, Python 2.6, Wx 2.8.12.1.
I don't receive the ' ImportError: No module named _core_ '
on initialization of my GUI but when a multiprocessing method is
called. If multiprocessing is deactivated the GUI works perfectly.
Wx._core_.pyd is included in the dist folder as well as all the needed
.dll files. The GUI also works perfectly on Mac with and without
multiprocessing activated. When built with Pyinstaller 1.5.1 on
Windows 7 the GUI doesn't throw the ' ImportError: No module named
_core_ ' but instead runs with a single core when asked to use
multiprocessing. Any thoughts on solving either of these problems so I
can have a full featured Windows executable?
It sounds like your problem may be similar to the one I had, reported in
http://www.pyinstaller.org/ticket/569: when an executable built with
PyInstaller executes another one (using Popen in my case), the
environment for the subprocess gets set up incorrectly, causing
_core_.pyd not to be found.
I'm using the 'develop' branch of PyInstaller, but you might have
success doing what I did to work around the problem (documented in the
ticket): essentially, get the folder support/loader/Windows-32bit from
the branch 'fix_merge_case' and replace the corresponding folder in your
PyInstaller installation. Let us know if it works.
--
Don Dwiggins
Advanced Publishing Technology
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
