Initial adaptations for Server API version 0.3.0 #1106
Draft
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
…different API versions
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
|
From Dev meeting: Move models to a separate PR to be merged in so server can import. |
|
Updated with testing for the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In order to prepare to transition to v0.3.0 of the Superstaq API, this PR adds a temporary
_SuperstaqClientobject (named_SuperstaqClient_v0_3_0which adheres to the new API and acss.job._Jobobject to work with it (an equivelant update for qiskit-superstaq will follow). This also involves adding agss._modelsmodule containing the send/receive data structures that are needed for the new API.This PR does not affect the current operation of any existing parts of client superstaq. A warning has also been added to indicate to users that using
v0.3.0is not stable and that they should continue usingv.0.2.0for now.