Are you directly importing psychopy.gui.qtgui, instead of just psychopy.gui? The latter is designed so that if Qt gives an import error it should silently fall back to wxpython for the dialog (which would explain your comment "the Psychopy GUI working without issue")

If Qt6 is now incompatible with Win7 I'm not sure what we'd be able to do to fix that btu if using wx gets around the problem I think we'll mark this as "won't fix"

Hi @peircej ,

The GUI in script is imported in standard way:

from psychopy import sound, gui, visual, <...>

To my knowledge, task script was created with GUI, and have standard imports.

Could it be a conflict between different versions of psychopy? We have several stand-alone versions of psychopy. For example script is run with python from standalone installations, but uses the libraries from different installation (or maybe default path)?

If Qt6 is now incompatible with Win7 I'm not sure what we'd be able to do to fix that btu if using wx gets around the problem I think we'll mark this as "won't fix"

I would prefer that you add ImportError to a except in qtgui.py, but our fix is quite easy, so I'm ok if you ignore that bug. I doubt there a lot of people that uses Win7 with several installations of psychopy.

OK, I now see what you mean about ImportError. It's because currently we only have ModuleNotFound error. So in your case the module is found but fails to import and that isn't trapped.

Sure, I think it's fine to make that change. Feel free to submit a pull request 👍