Skip to content

Conversation

@ScottCarda-MS
Copy link
Contributor

@ScottCarda-MS ScottCarda-MS commented Dec 29, 2025

Adds the cirq extra, qdk.azure.cirq, and qdk.azure.target.rigetti.

@ScottCarda-MS ScottCarda-MS changed the title Add Cirq and Rigetti content from azure.quantum to QDK package Dec 29, 2025
@ScottCarda-MS ScottCarda-MS marked this pull request as ready for review December 30, 2025 18:18
"azure-quantum>=3.5.0",
"qiskit>=1.2.2,<3.0.0",
"cirq-core>=1.3.0,<=1.4.1",
"cirq-ionq>=1.3.0,<=1.4.1",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need a separate cirq-ionq package? Is this similar to the qiskit-ionq dependency @idavis removed (https://github.com/microsoft/azure-quantum-python/pull/694/changes#diff-7be6800e2a7d73f55566f4819bbc22349cf365d410a0d50d3efe746b9c3c6e64)? If so, should we do something similar here?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Actually, I see this is a package by cirq itself (https://github.com/quantumlib/Cirq/tree/main/cirq-ionq), so possibly unrelated to the pattern that was used by qiskit-ionq)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are the requirements pulled from azure quantum: https://github.com/microsoft/azure-quantum-python/blob/main/azure-quantum/requirements-cirq.txt. @idavis suggested that we reference this dependency directly, though, by having the azure extra depend on azure-quantum[cirq], which is an idea I like as it removes the need for an additional "cirq" specific extra.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants