You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The qiskit-ibm-provider package is currently planned to be deprecated and removed at some point, with all its functionality moving to qiskit-ibm-runtime. When that happens, we should track through any extant deprecation warnings (especially in the 0.46 release) and make sure they suggest qiskit-ibm-runtime, not qiskit-ibm-provider, as alternatives / a potential provider when needed.
At the time of writing this issue, the only uses are in qiskit/__init__.py, but there may be more added during the 0.46 cycle.
When removing, we should search for references to qiskit-ibm-provider (the normal way the PyPI package is spelt) and qiskit_ibm_provider (how it's imported) to check for use in any code blocks.
Today, on the day of the 0.46.0 release, the only messages mentioning the IBM Provider are in the deprecation messages of qiskit.IBMQ, which I think it's fair to say IBMProviderwas a more direct replacement of. Since ibm-provider isn't fully merged to ibm-runtime, and we can always change the warning message in a patch release, I'll close this as complete for 0.46.0.
The
qiskit-ibm-provider
package is currently planned to be deprecated and removed at some point, with all its functionality moving toqiskit-ibm-runtime
. When that happens, we should track through any extant deprecation warnings (especially in the 0.46 release) and make sure they suggestqiskit-ibm-runtime
, notqiskit-ibm-provider
, as alternatives / a potential provider when needed.At the time of writing this issue, the only uses are in
qiskit/__init__.py
, but there may be more added during the 0.46 cycle.When removing, we should search for references to
qiskit-ibm-provider
(the normal way the PyPI package is spelt) andqiskit_ibm_provider
(how it's imported) to check for use in any code blocks.See Qiskit/qiskit-ibm-runtime#1285 for more detail.
The text was updated successfully, but these errors were encountered: