New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to execute script pyi_rth_qt4plugins #2207
Comments
having a similar issue with images not displaying on other computers. In my warnings I'm unable to import pyside. Installing it with pip doesn't fix the issue. My software works on many computers but some it won't show images. It may have something to do with qt4 plugins since pixmap has a set of plugins associated with that file |
Same thing then JSantos with PyQt4, win10, python 3.5.2 (32bits) and Pyinstaller developpement. |
compiled on windows10 python 3.5.2, compiles and runs file (pyside is not used or installed) but when running on client PC: During handling of the above exception, another exception occurred: Traceback (most recent call last): |
TLDR; On 64bit system install 64bit python and upgrade pip. (It worked on win7, python 3.4) I had the same problem, exe generated on win10, python 3.5.1, didn't work on win7.
When I tried to run my app from sources on this win7 computer with python 3.5.1 (previously installing PyQt from Unofficial Windows Binaries for Python
I guessed that it was because my Python was 32bit on 64bit system, so it installed packages with 32bit DLLs. |
Same problem for me here, Python 3.5.0 64bit on Windows7 64bit machine for development, run on a windows 7 64bit machine without Python and program crashes with same error as original post. Using the Pyinstaller current development version 3.3. Have tried to build exe with and without upx, have also tried including PyQt4 path in the spec file.....nothing works....please help |
@Marzybear maybe it's connected to Python version, try using 3.4 |
I reverted to python 3.4.4 and pyqt 4, 64 bit
I also stripped out a lot of unnecessary modules.
finally i was able to use pyinstaller with glitching.
We can now develop on windows 10 and deploy to same or windows 8, other
platforms not tested.
…On Tue, Jan 10, 2017 at 9:34 AM, Aleksander ***@***.***> wrote:
@Marzybear <https://github.com/Marzybear> maybe it's connected to Python
version, try using 3.4
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2207 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUEJL7SmNbaYAihp5uFOoRO4bwP_h1Dzks5rQ6UNgaJpZM4KKJfA>
.
|
Thanks so much!!!! It works on Python 3.4, PyInstaller 3.2 |
Works with Python 3.5 with PyInstaller 3.2 too. I had trouble installing PyInstaller on Python 3.4 because pywin no longer releases binaries for Python 3 versions below 3.5 as per mhammond/pywin32#1172. I would still would like to see Python 3.6 supported though. |
Closing as PyQt4 support has been removed since #5118. |
Packing applications with PyQt4 on Python 3.5 (64bit), Windows 10 with Pyinstaller 3.2 is resulting in errors when executed in other machines. Here is a minimalist app to illustrate this:
The resulting .exe works fine on this computer but on others throws the following error:
The error message is unclear since the PySide except exists only to check if it should be packed or not. I added two print statements to pyimod03_importers.py to identify what files were causing the error; it occurs when attempting to load PyQt4.QtCore, which corresponds to the file PyQt4.QtCore.cp35-win_amd64.pyd, which is correctly placed in the package/folder. The warnings file suggests that this might be due to submodule PyQt4.QtCore.QCoreApplication:
However, tweaking with the specs to explicitly bundle QtCore.QCoreApplication ends up with having it missing regardless.
The exact same script I provided, when packed with Pyinstaller 3.0 on Python 2.7, works correctly on my test Windows 10 machine with the default .spec settings. I have replicated this issue on a computer with a clean Python 3.5 install with the required libraries installed through pip to make sure this isn't just a problem on my installation's end.
Any ideas on what might be causing this?
The text was updated successfully, but these errors were encountered: