-
Notifications
You must be signed in to change notification settings - Fork 132
Prepare for Qiskit 2.0 by addressing removed classes and methods #1526
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
Merged
wshanks
merged 11 commits into
qiskit-community:main
from
wshanks:prepare-qiskit2-qobj-backendv1-rebase
Mar 7, 2025
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
4e2fda0
Remove references to BackendV1 following its removal in Qiskit 2.0
eliarbel c2ac105
Guard imports of BackendV1
wshanks 755f42b
wip: remove dependence on qobj/backendv1/backend.properties
wshanks ee47dda
black
wshanks 342e973
Remove stray inst_map references
wshanks 41340b4
Address MeasLevel/MeasReturnType
wshanks 7a16be0
black
wshanks 9987bb9
lint
wshanks 5274970
Release note
wshanks 1a11e89
Add deprecation warning for BackendV1
wshanks acbf2a6
Vendor deprecate_func and deprecate_arg from Qiskit
wshanks File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should at least add deprecation warning in here. I prefer completely removing BackendV1 usage because we cannot guarantee the rest of our software properly works with this backend.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The release note had a line about support for BackendV1 being removed in a future release, but I added an explicit
deprecationsentry about it as well. Also, I added a deprecation warning here. It is hard to do because this code gets called at varying levels of the stack and Python by default only shows deprecation warnings if the stack level is right. Python 3.12 added a coolskip_file_prefixesoption so I used that and it seemed to work well on 3.12+ -- it showed my user level code as responsible for the warning whether I createdBackendDatadirectly or created aT1experiment that createsBackendDatafour levels lower down in the stack. Users on <=3.11 might not see the warning depending on how they are usingBackendV1.My thought was that we are not planning much change to the repo in the near term and it was easy enough to hide the import here. Qiskit 1 will go out of support in six months and we don't need to support unsupported Qiskit versions, I think. I specified this in the deprecation note.