-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port Qiskit Metal from PySide2 to PySide6 #908
base: main
Are you sure you want to change the base?
Conversation
For ubuntu unit tests
Hoping this will resolve an issue with running tests and doc building
When this is merged, it will resolve #798. |
@priti-ashvin-shah-ibm @obrienpja Hi all, Is there any timeline on when this PR will be accepted? Best, |
I think we need a little help from somebody to test it on their end and make sure everything works as intended. Would you be up to help with this? |
I have tested this PR and it is not quite ready for acceptance since it fails on a number of tests... However I think I can resolve those issues and will make a PR with that instead. Best, |
That would be fantastic. Thank you. Keep us posted. |
@zlatko-minev I made the PR - #1002 (comment) - with the fixes. It passes all the automated checks and also my custom workflow checks. |
Great we'll move the discussion there |
What are the issues this pull addresses (issue numbers / links)?
Porting Qiskit Metal from PySide2 to PySide6
Did you add tests to cover your changes (yes/no)?
No, but I don't think we have any tests for the GUI itself anyway
Did you update the documentation accordingly (yes/no)?
No, none of the examples should be affected
Did you read the CONTRIBUTING document (yes/no)?
Yes
Summary
The commits change all of the PySide2 imports to PySide6 imports. It also changes the matplotlib backend from Qt5Agg to QtAgg.
Details and comments
A couple of classes were moved in PySide6. For example, QAction moved from QtWidgets in PySide2 to QtGui in PySide6. We also needed to change the backend that handles the rendering of matplotlib from Qt5Agg to QtAgg. According to their documentation, the QtAgg backend should be able to handle the connection between any version of Qt and matplotlib. From what I remember, they are doing their best to make it agnostic.