Fix #1062: ignore warning from a Cirq function about Qiskit #1063
Conversation
This file contains hidden or 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
The code in `src/openfermion/testing/wrapped.py` calls `cirq.testing.assert_implements_consistent_protocols`. The latter funtion prints warnings about the Cirq function `assert_qasm_is_consistent_with_unitary` when Qiskit is not installed. This is irrelevant to our testing; we don't do anything with QASM and we certainly don't want to introduce a dependency on Qiskit.
dstrain115
approved these changes
Jun 3, 2025
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.
The code in
src/openfermion/testing/wrapped.pycallscirq.testing.assert_implements_consistent_protocols. The latter funtion prints warnings about the Cirq functionassert_qasm_is_consistent_with_unitarywhen Qiskit is not installed. This is irrelevant to testing OpenFermion; OpenFermion doesn't do anything with QASM and we certainly don't want to introduce a dependency on Qiskit.Resolves issue #1062.