reorder qt support in kernel #560
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import priority: 1. ask matplotlib (if imported) - if PyQt4 specified, use API v1 2. ask QT_API - if pyqt specified, use API v2 3. if nothing specified, try PyQt4 v1, fallback on PySide.
QT_API now supersedes matplotlib rcParam, so the v2 API will always be used if QT_API=pyqt (as long as matplotlib isn't too old) Default behavior for no QT_API is unchanged
|
Thank you for your effort in working around this mess, Min. This pull request looks good to me, although I have not tested it out myself. |
|
I have merged the corresponding changes to mpl master. |
|
Excellent! I'll update my matplotlib, and test a few cases before merging. -MinRK On Jul 7, 2011, at 11:57, efiringreply@reply.github.com wrote:
|
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this pull request
Nov 3, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
import priority:
So, Qt fragmentation is apparently a total mess, but this default priority seems to make sense.
When using
pylab=qt, it will respect the proposed rcParam 'backend.qt4', which could be either 'PyQt4' or 'PySide'. If it is PyQt4, then the v2 API is not set. If matplotlib is <= 1.0.1, then PyQt4 is always used.When using
gui=qt, the ETS QT_API env variable is respected. If QT_API=pyqt, then PyQt is used with API v2 for compatibility with ETS 4.0. If QT_API is not set, then the default is to use PyQt with the default API version, and if PyQt is unavailable, PySide will be tried as a fallback.This means that if you have everything installed, QT_API is a ternary switch:
unspecified: PyQt4 v1
'pyqt' : PyQt4 v2
'pyside' : PySide
I also added a section to the reference doc, covering some of this mess.