I've been using py2exe, relatively happily with Python 2.4, but when I switched to Python 2.6 I couldn't get rid of a few annoying bugs.
The first annoying problem related to shell.pyd, and there's a 'magic' hack that you can apply to get rid of this: http://www.py2exe.org/index.cgi/win32com.shell Under 2.6 the hack only seems to work for one of my .py scripts, not another one. I'll have to use another dirty hack to get around that I guess. My project has multiple python files which I want to turn into multiple EXEs, and I want those EXEs to share as much of the Python 'stuff' as possible. With the change to Python 2.6 modules suddenly stopped including the right directories in the module path, meaning they couldn't find the .pyd files for the bundle_files=3 option, so I bizarrely found I had to start adding lines like sys.path.append(".\ \") to make stuff work. Another thing about py2exe, it seems like it's a slowly dying project, and with the last release in 2008, is it just not worth bothering with, and can pyInstaller be considered something of a new defacto standard for bundling? I make use of TKInter, ctypes and comtypes. It's going to be a fair amount of work to switch, I know I'm probably asking in the wrong group if I want an unbiased opinion, but is pyInstaller the panacea I'm looking for? many thanks, Biff. -- 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.
