[Flent-users] PyQt returns SystemError when loading GUI on OS X

2019-07-16 Thread Toke Høiland-Jørgensen
Hi I'm the maintainer of the Flent tool, which uses PyQt for its GUI. I recently got a bug report which showed odd behaviour on OS X. Specifically, setupUi() returns: SystemError: returned a result with an error set With what appears to be an underlying: AttributeError: __getattribute__ The

Re: [Flent-users] [tohojo/flent] Unable to use flent-gui from 83d14d68 (#167)

2019-07-16 Thread Sebastian Moeller
Thank you very much, both Toke ans Pete: QT_API=pyside2 ./run-flent --gui did the trick, now I guess I either write a small wrapper around run-flent or simply put the export in my .bashrc. Anyway with this the GUI runs and loads data files again. Again Best Regards & Thanks > On Jul 16,

Re: [Flent-users] [tohojo/flent] Unable to use flent-gui from 83d14d68 (#167)

2019-07-16 Thread Pete Heist
It looks like it was still using PyQt5 in your case, so make sure to first do: ``` export QT_API= pyside2 ``` If this is a long-term fix for Mac, maybe that var could be set on MacOS when sys.platform is darwin, assuming we have a chance to do so before those libs are initialized. Probably

Re: [Flent-users] [tohojo/flent] Unable to use flent-gui from 83d14d68 (#167)

2019-07-16 Thread Toke Høiland-Jørgensen
Sebastian Moeller writes: > Mmmh, so I installed qtpy (and dependencies) I now get: > > ./run-flent --gui > Started Flent 1.9.9-git-43e16d5 using Python 3.7.4. > Initialised matplotlib v3.1.1 on numpy v1.16.4. > GUI loaded. Using Qt through pyqt5 v5.12.3. > objc[13628]: Class

Re: [Flent-users] [tohojo/flent] Unable to use flent-gui from 83d14d68 (#167)

2019-07-16 Thread Pete Heist
``` export QT_API=pyside2 ``` A space had crept in my previous post after the equals. :) -- You are receiving this because you commented. Reply to this email directly or view it on GitHub:

Re: [Flent-users] [tohojo/flent] Unable to use flent-gui from 83d14d68 (#167)

2019-07-16 Thread Toke Høiland-Jørgensen
Pete Heist writes: > It looks like it was still using PyQt5 in your case, so make sure to first do: > > ``` > export QT_API= pyside2 > ``` > > If this is a long-term fix for Mac, maybe that var could be set on > MacOS when sys.platform is darwin, assuming we have a chance to do so > before those