Adapting TQ with New Qiskit Deprecations #235
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
Sounds good to me, does 1.0.0 have a lot of interface changes? |
|
I think the biggest change that I immediately saw was qiskit-aer is changed, so that would require a bit more looking into. Full release notes: https://docs.quantum.ibm.com/api/qiskit/release-notes/1.0 |
|
And nice, it looks like we’re passing now! Should be good to merge in! |
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.
For the upcoming deadline, I’m keeping qiskit < 1.0.0 but have been working on refactoring the completely deprecated IBMQ aspect.