-
Notifications
You must be signed in to change notification settings - Fork 317
WinPython Control Panel crashes after replacing PyQt5 with PyQt4 #483
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
Comments
It should work, and indeed it doesn't ... inquiring what I did wrong (again). For example:
|
a longer term solution would be to rely on QtPy, or have WPPM not relying on Qt packages. |
The most important thing to me is that WinPython continues to support replacing PyQt5 with PyQt4. The WinPython 3.5.3.0Qt5 issue I found isn't causing me a real problem because I have a work-around. No hard feelings... I did some more testing today with Spyder+matplotlib+PyQt5, and I posted the results at matplotlib/matplotlib#7688 |
WinPython shall support PyQt4, or diversity, as PySide2 should become an option, sometime next year. |
I customize the batch file for starting Spyder in each WinPython installation folder. Where WinPython has PyQt4 installed, I have "set QT_API=pyqt". Where WinPython has PyQt5 installed, I have "set QT_API=pyqt5". |
The default test I do is the "generic" one everybody does... So I'll tweak it as written before, but the true solution is to stop patching PyQt5. |
Using 64-bit WinPython 3.5.3.0Qt5 on Win8.1, I did the following:
The result is that WinPython Control Panel process terminates. I worked around the problem by deleting the folder "%WINPYDIR%\Lib\site-packages\PyQt5".
Perhaps the problem occurs because PyQt5 is in the path before PyQt4, and uninstalling PyQt5 leaves a DLL. How about changing env.bat to use different paths for the PyQt5 and PyQt4 cases?
By the way, I am using PyQt4 because I continue to have this problem: matplotlib/matplotlib#7688
I would have re-opened this issue: #449
But the WinPython project does not allow users to do this.
The text was updated successfully, but these errors were encountered: