-
Notifications
You must be signed in to change notification settings - Fork 56
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
vitables fails to launch with "cannot import name 'loadUiType' from 'qtpy.uic'" #97
Comments
My PyQt5, qtpy, pyside and sip were installed with the system package manager. When I uninstalled those and allowed pip3 to pull in vitables dependencies, this is what it did:
However, vitables still does not start
So it seems like (1) vitables absolutely needs pyside, and (2) despite pip3 saying that PyQt5 got installed, vitables can't find it. |
Well, it seems that something is messy in your system. You say that have uninstalled PyQt5, qtpy, pyside and sip and then installed vitables via pip3. In that case the expected result is a new installation of PyQt5 (and sip) and qtpy because they are vitables dependencies. However the output of your pip3 install vitables command says that PyQt5 (and sip) and qtpy were already satisfied dependencies and the only installed package is vitables. I've done the same thing (in a virtual environment, not with the system Python) and got the following result:
Then I've run the vitables command and ViTables runs just fine (pyside is not installed in the virtual environment). The second thing that confuses me is: if PyQt5 is installed (because apparently it was not uninstalled) and Pyside is probably installed too (because its uninstallation also failed) then why qtpy cannot find any Qt bindings? The only thing that comes to my mind is that for some reason pyside, pyqt5 and qtpy have not been properly installed/uninstalled/installed again and they are somehow broken. My advice is the same that gave you in #96: install vitables in a new, fresh virtual environment, you don't need pyside at all. Unfortunately I have not a MacOs X for testing vitables so I think I cannot give you more help. Anyway, if your problem persists just let us know. Maybe some other user will be able to help you. |
So I did a very careful cleanup of my system to get rid of all PyQt5, PyQt5-sip and qtpy, and did and
Running vitables after that worked, so all is well! I was trying to have one maintaining system for python packages, between macports and pip3, which is why I tried installing the PyQt5 stuff through macports initially. I guess it was not to be... |
I installed qtpy and PyQt5 through my system's package manager, and vitables with
pip3 install vitables
, but when I try to start it,I know that both qtpy and PyQt5 are installed for the python installation vitables is running in:
And yet vitables won't start. To see what was going on, I tried putting a print statement in
/Users/sbasu1/packages/macports/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/qtpy/uic.py
, like soand sure enough, both of them were
False
. So I'm not sure why vitables won't work. Any help would be appreciated.The text was updated successfully, but these errors were encountered: