-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Remove already "removed" FakeBackendV2
#11997
Conversation
One or more of the the following people are requested to review this:
|
Pull Request Test Coverage Report for Build 8702630119Details
💛 - Coveralls |
FakeBackendV2
FakeBackendV2
### Summary In qiskit 0.46, several classes in the `qiskit.providers.fake_provider` module were deprecated, including `qiskit.providers.fake_provider.fake_backend.FakeBackendV2`. However, the removal PR failed to address this particular class, so while this particular `FakeBackendV2` was no longer part of the public API, the import path would still work. This oversight will be addressed in Qiskit/qiskit#11997, but in order to merge this PR we must make sure that all the downstream libraries covered by `qiskit-neko` are up-to-date with the change. This change adds an alternative import path for this class in qiskit-experiments. It follows the pattern from other 1.0 import deprecations. The removal would roll out in the 1.1 release, but it is indicated as a 1.0 removal because that is when it should have technically taken place. ### Details and comments Blocks Qiskit/qiskit#11997.
### Summary In qiskit 0.46, several classes in the `qiskit.providers.fake_provider` module were deprecated, including `qiskit.providers.fake_provider.fake_backend.FakeBackendV2`. However, the removal PR failed to address this particular class, so while this particular `FakeBackendV2` was no longer part of the public API, the import path would still work. This oversight will be addressed in Qiskit/qiskit#11997, but in order to merge this PR we must make sure that all the downstream libraries covered by `qiskit-neko` are up-to-date with the change. This change adds an alternative import path for this class in qiskit-experiments. It follows the pattern from other 1.0 import deprecations. The removal would roll out in the 1.1 release, but it is indicated as a 1.0 removal because that is when it should have technically taken place. ### Details and comments Blocks Qiskit/qiskit#11997. (cherry picked from commit 428c9bc)
With qiskit-community/qiskit-experiments#1420 merged, an |
We would need qiskit-experiments to do a bugfix/patch release so that neko can pull the fix for its test. I'll ping them about it. |
The patch release of qiskit-experiments is out! The PR can now be merged. |
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.
I confirmed this is not in the docs anywhere and was just an oversight for removal in 1.0. Heh, but you really like to test the stability policy between this and #12042 (review)
Summary
This PR fixes an oversight from #11376 where the
FakeBackendV2
base class was removed from the documentation and reported as removed without actually removing the source code for the class (the fact that there were twoFakeBackendV2
classes probably didn't help). I'm labeling it aschangelog:None
because this change doesn't affect the public API.Details and comments
On hold until a
qiskit-experiments
release that includes qiskit-community/qiskit-experiments@428c9bc. This allow the correspondingqiskit-neko
tests to pass.