Fix Qt with PySide6 6.4.0 #24158
Merged
Fix Qt with PySide6 6.4.0 #24158
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
QuLogic
force-pushed
the
fix-qt
branch
2 times, most recently
from
f97180f
to
389b45f
Compare
oscargus
approved these changes
Oct 14, 2022
1 task
meeseeksmachine
pushed a commit
to meeseeksmachine/matplotlib
that referenced
this pull request
Oct 15, 2022
oscargus
added a commit
that referenced
this pull request
Oct 15, 2022
…158-on-v3.6.x Backport PR #24158 on branch v3.6.x (Fix Qt with PySide6 6.4.0)
This was referenced Nov 1, 2022
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.
PR Summary
I also set the "Minimum versions" job to test the minimum supported versions of all the Qt bindings. Due to bugs in PySide2, I had to set its minimum to 5.14 instead of 5.11.2 like PyQt5.
Fixes #24155.
PR Checklist
Tests and Styling
pytestpasses).flake8-docstringsand runflake8 --docstring-convention=all).Documentation
doc/users/next_whats_new/(follow instructions in README.rst there).doc/api/next_api_changes/(follow instructions in README.rst there).