-
Notifications
You must be signed in to change notification settings - Fork 127
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
Provider class was deprecated in qiskit 1.1 #1488
Comments
### Summary Qiskit 1.1 deprecated the Provider abstract class to be removed in 2.0 (planned for 1Q2025). In those cases where the class is used for only typechecking purposes, the import should only happen when `TYPE_CHECKING`. For the rest of the cases, I opened #1488
### Summary Qiskit 1.1 deprecated the Provider abstract class to be removed in 2.0 (planned for 1Q2025). In those cases where the class is used for only typechecking purposes, the import should only happen when `TYPE_CHECKING`. For the rest of the cases, I opened #1488 (cherry picked from commit 519bb53)
…1489) (#1490) ### Summary Qiskit 1.1 deprecated the Provider abstract class to be removed in 2.0 (planned for 1Q2025). In those cases where the class is used for only typechecking purposes, the import should only happen when `TYPE_CHECKING`. For the rest of the cases, I opened #1488 <hr>This is an automatic backport of pull request #1489 done by [Mergify](https://mergify.com). Co-authored-by: Luciano Bello <[email protected]>
Ah, I see why this hasn't raised a deprecation warning in the tests: qiskit-experiments/qiskit_experiments/test/fake_backend.py Lines 26 to 45 in 519bb53
|
qiskit-experiments uses
Provider
abstract class significantly. In the cases I checked, it seems to use it as part of the Backend property to get account and job data.In qiskit 1.1, upstream decided to deprecate the class and they are going to remove it in qiskit 2.0 (coming in 1Q2025).
The text was updated successfully, but these errors were encountered: