Hi all,
Thanks for your work on pyinstaller. I have had good results with
pyinstaller-1-4-rc1 and python 2.5 for some time now.
Due to upstream changes in GNUmed 1.1.6 which I am trying to package I had to
move to pyinstaller 1.5.1 and upgrade python along the way. I upgraded to
python 2.7.
Running the newly created build environment did not produce a working
executable as it had done before.
When setting the debug flag in pyinstaller I noticed that it is now required to
install pywin32. I downloaded and installed the corresponding version for
python 2.7 from sf.net.
in a terminal in Windows XP I can successfully issue command such as
import win32api.
Rebuilding GNUmed and running it shows this:
#############################################
C:\workplace\gnumed-client.1.1.6\gnumed.exe
Found embedded PKG: C:\workplace\gnumed-client.1.1.6\gnumed.exe
Extracting binaries
manifestpath: C:\workplace\gnumed-client.1.1.6\gnumed.exe.manifest
Error activating the context
python27.dll
Manipulating evironment
PYTHONPATH=C:/workplace/gnumed-client.1.1.6
v
# installing zipimport hook
import zipimport # builtin
# installed zipimport hook
importing modules from CArchive
import marshal # builtin
extracted iu
import imp # builtin
import nt # builtin
extracted struct
import _struct # builtin
extracted archive
Installing import hooks
outPYZ1.pyz
Running scripts
import zlib # builtin
import _codecs # builtin
import errno # builtin
import _weakref # builtin
Traceback (most recent call last):
File "<string>", line 34, in <module>
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 436, in importHook
mod = _self_doimport(nm, ctx, fqname)
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 521, in doimport
exec co in mod.__dict__
File "C:\workplace\gnumed-
client.1.1.6\build\pyi.win32\setup\outPYZ1.pyz/win32
com", line 5, in <module>
File "C:\workplace\pyinstaller-1.5.1\iu.py", line 455, in importHook
raise ImportError, "No module named %s" % fqname
ImportError: No module named win32api
RC: -1 from win32comgenpy
OK.
####################################
Can anyone point me in the right direction ?
The spec file looks like this.
####################################
# Process the includes and excludes first
data_files = []
includes = []
excludes = ['_gtkagg', '_tkagg', 'bsddb', 'curses', 'pywin.debugger',
'pywin.debugger.dbgcon', 'pywin.dialogs', 'tcl',
'Tkconstants', 'Tkinter']
packages = []
dll_excludes = []
dll_includes = []
# Set up the more obscure PyInstaller runtime options
options = [('v', '', 'OPTION')]
# This is a place where the user custom code may go. You can do almost
# whatever you want, even modify the data_files, includes and friends
# here as long as they have the same variable name that the setup call
# below is expecting.
# No custom code added
# The setup for PyInstaller is different from py2exe. Here I am going to
# use some common spec file declarations
analysis = Analysis(['C:
\\workplace\\pyinstaller-1.5.1\\support\\_mountzlib.py', 'C:
\\workplace\\pyinstaller-1.5.1\\support\\useUnicode.py',
'C:\\workplace\\gnumed-client.1.1.6\\client\\gnumed.py'],
pathex=[],
hookspath=[],
excludes=excludes)
pyz = PYZ(analysis.pure, level=9)
executable = EXE(pyz,
analysis.scripts + includes + packages + options,
exclude_binaries=1,
name=r"gnumed.exe",
debug=True,
console=True,
strip=False,
upx=False,
icon=r'C:\workplace\misc\serpent.ico',
version=None)
collect = COLLECT( executable,
analysis.binaries - dll_excludes + dll_includes + data_files,
name=r"c:/workplace\gnumed-client.1.1.6\frozen\bin",
strip=False,
upx=False)
# This is a place where any post-compile code may go.
# You can add as much code as you want, which can be used, for example,
# to clean up your folders or to do some particular post-compilation
# actions.
# No post-compilation code added
# And we are done. That's a setup script :-D
##################################
I used ArchiveViewer.py to check the contents of outPYZ1.pyz
It seems there is no win32api stuff in there. I can see some references to
win32com
The output directory of the exe file (where all the dll and pyd files are) has
a
file called win32api.pyd
Python is not in the PATH on Windows XP.
Any help is appreciated.
Sebastian Hilbert
--
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.
