Fantastic. PyInstaller 2.0 does work with PySide.
I had a little encouragement from Laurence (thank you sir) so with a few tweaks resulting in the set of imports below, now a single exe importing PySide does work. This is the command I'm using: pyinstaller-2.0> PyInstaller -F C:\_zoo\vgp18g.py I do not know whether all of these imports are being done the best way, just that the exe builds and runs. Yay! ------------------------------------------------------------------- from PySide import QtCore, QtGui from PySide.QtCore import QSettings, Qt from PySide.QtGui import QApplication, QLineEdit, QCursor import pprint.pprint as pp import SendKeys.SendKeys as SendKeys import os, sys, re, time, random import subprocess, psutil import win32clipboard, win32con, win32gui, win32process from _winreg import EnumValue, OpenKeyEx, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, KEY_READ ------------------------------------------------------------------- I'm using Python 2.7 and building on 32-bit XP currently. The program has over 4000 lines in it. Exe size turns out to be about 7.59 MB by the way. For those who want to work with PyInstaller together with PySide, I believe the following is probably all true and at least some of these might be important for you to know: The installs of PySide via easy_install vs PySide-1.1.1qt474.win32-py2.7.exe for example are not created equal. One will result in an egg directory and in my experience that is problematic. Instead, go for the full PySide directory under C:\Python27\Lib\site-packages with all of its files visible (rather than wrapped into an egg file or directory), and with no PySide entry in easy-install.pth. If you already have an egg file, you can rename it .zip and extract the files, however PySide-1.1.1qt474.win32-py2.7.exe might be the better/simpler way to go. I do have a directory called PySide-1.1.1qt474-py2.7.egg-info, however I renamed it .off just now and tried again with no problem. So, just to try to help make this crystal clear, among other files, these are a few of the files in that directory, to give you the general idea: C:\Python27\Lib\site-packages\PySide\pyside-python2.7.dll C:\Python27\Lib\site-packages\PySide\pyside-python2.7.lib C:\Python27\Lib\site-packages\PySide\QtCore.pyd C:\Python27\Lib\site-packages\PySide\QtCore4.dll C:\Python27\Lib\site-packages\PySide\QtGui.pyd C:\Python27\Lib\site-packages\PySide\QtGui4.dll C:\Python27\Lib\site-packages\PySide\shiboken-python2.7.dll C:\Python27\Lib\site-packages\PySide\shiboken-python2.7.lib C:\Python27\Lib\site-packages\PySide\shiboken.exe C:\Python27\Lib\site-packages\PySide\shiboken_generator.dll C:\Python27\Lib\site-packages\PySide\ssleay32.dll C:\Python27\Lib\site-packages\PySide\__init__.py C:\Python27\Lib\site-packages\PySide\__init__.pyc C:\Python27\Lib\site-packages\PySide\__init__.pyo > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Martin Zibricky > Sent: Monday, August 13, 2012 8:30 AM > To: [email protected] > Subject: Re: [PyInstaller] PyInstaller 2.0 and PySide > > Gary Hawkins píše v St 08. 08. 2012 v 23:51 -0700: > > Should it work with PySide now? > > No, 2.0 won't work with pyside. Some contributors started working on > that in some forks on github. > > But no one submitted a merge request yet and we do not have men power > for that. > -- 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.
