This behavior is due to the fact that the Enthought Tool Suite is
(trying) to use PyQt API #2 but, before that, Spyder's machinery has
already imported PyQt with the default API (which is API #1 with
Python 2.x).
To avoid this behavior, you just have to prevent Spyder from importing
PyQt. Depending on the Spyder's version that you are using, it means
that you have to disable the "Remove PyQt Input Hook" option and the
"Matplotlib patch" option - and eventually the "Monitor" features (all
these options are available from the preferences panel).
HTH,
Pierre
> --
> You received this message because you are subscribed to the Google Groups "spyder" group.
> To post to this group, send email to spyd...@googlegroups.com.
> To unsubscribe from this group, send email to spyderlib+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
>
> Thanks,
>
> Turning off the "Remove PyQt input hook" seemed to fix the problem. I
> also found the "Patch Matplotlib figures," but that unchecking that
> did not seem to be immediately necessary. Both of those were on the
> Console/External modules form. I did not find the "Monitor" features.
Monitor settings are in the 'Introspection/...' tab of Console preferences.
> I'm curious as to capability I lose by disabling these options. Would
> it be better to change the default backend for either Matplotlib or
> ETS?
Actually there is no other solution as ETS only supports PyQt API #2.
But if you don't have to disable the Monitor features, that's really
not a problem: the other two options are not so important.
-Pierre
I have implemented a new option in Console preferences to select PyQt
API version number at runtime. This should avoid those issues - at
least I've tested this with almost the same configuration as yours.
It requires the latest development version of Spyder.
HTH
Pierre