Hi Giovanni,
thanks, I reproduced the problem and came up with a fix which works for
me so far (tested under Windows XP and 7). The fix is already committed
in the latest py26win; cool thing is it seems to also fix an issue with
matplotlib.
You were right, it was the change in Python distutils you pointed out
which broke things. Possible solutions I tried was adding a manifest
with MSV90 as dependent assembly directly to the pyinstaller generated
executable, but this had the drawback of requiring the MSVC90 CRT to be
installed on the system where the exe runs, so I scrapped that idea
eventually and now instead 'fix' the manifests of the binaries in
pyinstaller's bincache folder by adding any dependent assemblies of
python.exe to the embedded manifest of the cached files (for Python 2.6,
this boils down to MSVC90, but I thought it would be a good idea to make
it a bit future-proof). This seems to work, and should not break
one-file deploys. You will need to delete the old bincache folder after
updating to the latest py26win. Let me know if it works.
Am 21.04.2010 14:55, schrieb Giovanni Bajo:
On Wed, 2010-04-21 at 12:13 +0200, Florian Höch wrote:
Ok, I've now upgraded to Python 2.6.5. I've tried a few modules (not
built myself) with pyds (numpy 1.4.0, PyQt4 4.5.4-1, wxPython 2.8.10.1),
all working as far as I can tell. Can you give an example?
Try installing this module from source:
pypi.python.org/pypi/greenlet
compile it yourself with Visual Studio 2008 through "setup.py build".
Then write a simple "import greenlet" program and pack it with
PyInstaller (one-file). It does not work for me.
--
Florian Höch
--
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.
