It is definitely a problem of the tables package in combination with MinGW. I guess, you are using compiled binary packages.
With the following combination of packages, I can reproduce your problem: python-2.6.6.msi numpy-1.5.1-win32-superpack-python2.6.exe numexpr-1.4.1.win32-py2.6.exe tables-2.2.1.win32-py2.6.exe PyQt-Py2.6-x86-gpl-4.8.2-1.exe --- The following combination works as expected: python-2.6.6.msi numpy-1.3.0-win32-superpack-python2.6.exe tables-2.1.2.win32-py2.6.exe PyQt-Py2.6-x86-gpl-4.8.2-1.exe --- Try to build the tables package from source. If you only need 32 bit executables, you should give the free Microsoft Visual C++ 2008 Express Edition a try. With Visual C++ 2008, it runs without problems (using tables-2.2.1). Ulli -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Vicent Mas Gesendet: Dienstag, 11. Januar 2011 20:30 An: [email protected] Betreff: [PyQt] Fwd: VendorId issue Hi, Thanks for your reply. I've found the module causing problems. It is the tables module from the PyTables package. What I've done is to write a very simple python script, launcher_script.py, which imports QtGui and tables modules. They both live under the site-packages directory. Then I've created an executable from this script using the MingW capable version of sib.py. As you can see in the attached output.txt, sib can deal properly with PyQt4 but not with the tables module. Importing the tables module from a python console works fine so it seems that the problem is in the sib program but I don't know how to fix it. I've attached the script used for this test, the MingW capable sib.py I use for generating the executable and the output produced for the executable script created with sib.py. The executable has been created with: $ python sib.py -M -c -v -u ./launcher_script.py and the output with $ launcher_script.exe -w -v Could you provide some more help for solving this problem, please? Thanks in advance. Vicent PS: Ulli, sorry for my previous sending as a personal mail. 2011/1/11 Ulrich Berning <[email protected]>: > Try to build it as a console application (-c) with support for the > verbose flag (-v). Then start it with -vv and look at the output. This > may identify the problems. > > Ulli > > -----Ursprüngliche Nachricht----- > Von: [email protected] > [mailto:[email protected]] Im Auftrag von Vicent Mas > Gesendet: Montag, 10. Januar 2011 18:03 > An: [email protected] > Betreff: [PyQt] VendorId issue > > Hi, > > I'm trying to make an executable for the launcher script of my pyqt > application. I'm using the mingw version of sib.py (from the VendorId > package) but I've found some problems when importing modules that I > don't know how to fix. This used to work fine in the past, when my > application only supported python 2.5 and PyQt 4.6 (IIRC). Now I've > moved to python 2.6 and pyqt 4.8.2 and the executable built via sib.py > is unable to import my application modules (although they are > installed in the standard c:/python26/lib/site-packages directory and > I can import them with no problems from a python console). I've just > realized that the VendorID package is rather old so maybe it doesn't > support python2.6 and/or current versions of PyQt. Could someone tell > me if I'm right? > > Thanks in advance, > > Vicent > > -- > Share what you know, learn what you don't. > _______________________________________________ > PyQt mailing list [email protected] > http://www.riverbankcomputing.com/mailman/listinfo/pyqt > > _______________________________________________ > PyQt mailing list [email protected] > http://www.riverbankcomputing.com/mailman/listinfo/pyqt > -- Share what you know, learn what you don't. _______________________________________________ PyQt mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/pyqt
