Open tomgoddard opened 1 year ago
Thanks! This is what I have done in the 0.2.2X1.4 branch in response to this issue https://github.com/charbj/wiggle/issues/1.
I have been testing that for a while, and it seems to be okay (nothing has broken so far). So I may merge this into the main branch and close this issue.
CBJ
Oops! I should have checked earlier issues to see if this was already discussed. I do think it is pretty safe to switch over to the imports from Qt instead of PyQt6. Most ChimeraX users should be using ChimeraX 1.4 so having the main branch only work on 1.3 will discourage some people.
I see Wiggle is directly using PyQt5 which is what ChimeraX 1.3 used. But the current ChimeraX 1.4 (released in June 2022) uses PyQt6. The way this is handled in ChimeraX is anywhere you would import from PyQt5 instead import from Qt. For example instead of
use
This relies on the fact that PyQt6 and PyQt5 are almost compatible. Hopefully they will be fully compatible for the uses Wiggle makes. I changed the imports in wiggle and also changed QtCore.pyqtSignal to QtCore.Signal and the user interface displayed but I have not tested that it all functions.
Here is the error trying to use Wiggle in a current ChimeraX daily build (that will become ChimeraX 1.5 expected to be released at the end of October or in November 2022).