add PySide to interactive_bk list #3386
Closed
Conversation
This file contains hidden or 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
|
Is PySide even a name of a backend? I know we can use it when using Qt-based backends, but I didn't think it was actually a valid name for a backend. |
|
There is no pyside backend. The qt4agg backend can use either pyqt4 or pyside. @jbmohler, how did PySide get written to the default rc file? That is the real bug. |
|
It's doing this on a windows build that has PySide (not PyQt) and no tcl/tk. You might ask how I got to that point ... the answer is jbmohler@ccd95fd which doesn't yet have tcl/tk support but should. That commit is my current results of fixing #1717 Another answer to your question might be https://github.com/matplotlib/matplotlib/blob/master/setupext.py#L2021 . Should name = "pyside" by name = "qt4agg" ? |
|
Closing in favor of #3387. |
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 cann
2C90
ot 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.
This fixes what seems to me to be a straight-forward omission of PySide in the list of valid back ends. I discovered it while building in a context where PySide was the only available gui backend and "PySide" got written to the default rc file.