Open hoechenberger opened 4 months ago
Here's how I fixed the drag and drop issue: https://github.com/cbrnr/mnelab/commit/4b65c817e7ce3989f44c5b5cc94c88da8d905996
Is that the same bug? The error is:
--> 383 def dragEnterEvent(self, event: QtGui.QDragEnterEvent) -> None:
which comes from an AttributeError:
AttributeError: module 'PySide6.QtPrintSupport' has no attribute 'QDragEnterEvent'
In other words, I think QtGui.QDragEnterEvent
in the code is somehow showing up as PySide6.QtPrintSupport.QDragEnterEvent
, i.e., the QtGui
is messed up somehow.
This looks like https://bugreports.qt.io/browse/PYSIDE-2674 . It manifested by trying to do stuff like QtGui.<something>
and having it look for the attribute on the wrong object as well. They say they fixed it, but this issue thinks that they maybe didn't fully...
That's weird. Maybe mention in that bug report that the problem still occurs in 6.7.1 (because it claims that it has been fixed in that version)?
Re is that the same bug, it could be, it also showed an incorrect class hierarchy for me. But maybe this was just a problem in this particular method, which I could fix (possibly by working around it)... I remember thinking that it was really weird that somehow the inheritance tree was all messed up, but then didn't look into it further because my original issue had been fixed (worked around). So I'd be really interested if this is a larger issue!
@larsoner Just to be absolutely sure, could you kindly try to reproduce this? I was trying to ensure that I wasn't mixing different installations of Qt and respective bindings, but maybe I messed up. Maybe this is an installation mistake on my end, or a conda packaging problem (even though I installed everything except for Python from PyPI, at least to my knowledge)
I just reproduced it in https://github.com/mne-tools/mne-python/pull/12629 when I tried to remove the existing !=6.7.1
. For some I can't get to the traceback on Azure but it's the same as the one here.
Hello, it seems pyvistaqt is not compatible with PySide 6.7, even though there is no upper bound for this dependency.