Move `qiskit.test.mock` to `qiskit.providers.fake_provider` and deprecate
See original GitHub issueIn #7437 we began the process of moving the features in qiskit.test.mock
to qiskit.providers.fake_provider
, by making them accessible at the new name. We can’t issue deprecation warnings in Terra 0.20, but between 0.20 and 0.21 we should ensure that all our internal uses point to the new names, and then implement the deprecation warning.
This is on hold until after Terra 0.20 has released.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Fake Provider ( qiskit.providers.fake_provider )
The fake provider module contains fake providers and fake backends classes. ... which are useful for testing the transpiler and performing noisy simulation ......
Read more >Release Notes - Qiskit
Qiskit Metapackage Version qiskit‑terra qiskit‑aer qiskit‑ibmq‑provider Release Date
0.39.4 0.22.3 0.11.2 0.19.2 2022‑12‑08
0.39.3 0.22.3 0.11.1 0.19.2 2022‑11‑25
0.39.2 0.22.2 0.11.1 0.19.2 2022‑11‑03
Read more >Release Notes — Qiskit 0.36.0 documentation
Qiskit Metapackage Version qiskit‑terra qiskit‑aer qiskit‑ignis qiskit‑ibmq‑provider Release...
0.36.0 0.20.0 0.10.4 0.7.0 0.19.0 2022‑04...
0.35.0 0.20.0 0.10.3 0.7.0 0.18.3 2022‑03...
0.34.2 0.19.2 0.10.3 0.7.0 0.18.3 2022‑02......
Read more >FakeProvider - Qiskit
Fake provider containing fake V1 backends. Only filtering backends by name is implemented. This class contains all fake V1 backends availabe in the...
Read more >qiskit.providers
After that the standard deprecation policy will apply to that interface version. This will give providers and users sufficient time to adapt to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, the import structure you mentioned is exactly right. You can also add the deprecation warnings inside
qiskit.test.mock
as well. We should leave that possible path in place for quite a long time, because the fake backends are already commonly used, and we want to give people lots of time to respond.For the release notes: yeah, no need to change any of those references. If there are any old
.. jupyter-execute::
blocks that useqiskit.test.mock
in the release notes, you can just swap those to.. code-block:: python
instead - it’s ok if super old code in release notes doesn’t execute any more.Yes, please!