This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
Vendor Qiskit's pubsub implementation
#799
Merged
Conversation
This file contains 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
Qiskit 1.0 is removing this, so applications that want to continue using it (within themselves; Qiskit will no longer be a central broker) should arrange for a centralised location for their published events. This vendors the code into the IBM Provider, from which Runtime can then re-import. For backwards compatibility, the IBM Provider's `_Broker` singleton will resolve to the Qiskit one, if a version of Qiskit that supplies it is installed. This means that the package remains compatible with code that still accesses the `Subscriber` via Qiskit (e.g. an un-upgraded IBM Runtime).
Pull Request Test Coverage Report for Build 7613694488
💛 - Coveralls |
kt474
approved these changes
Jan 22, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Qiskit 1.0 is removing this, so applications that want to continue using it (within themselves; Qiskit will no longer be a central broker) should arrange for a centralised location for their published events. This vendors the code into the IBM Provider, from which Runtime can then re-import.
For backwards compatibility, the IBM Provider's
_Brokersingleton will resolve to the Qiskit one, if a version of Qiskit that supplies it is installed. This means that the package remains compatible with code that still accesses theSubscribervia Qiskit (e.g. an un-upgraded IBM Runtime).Details and comments