Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add support for `qir.v1` input data format for cirq Targets

Open
#650 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, python
Domain
cloud

Research direction

Start by reading azure.quantum.cirq.targets.Target and compare it with the AzureQirBackend extension of azure.quantum.qiskit.backends.AzureBackendBase. Determine how qir.v1 input is handled there and what equivalent Cirq target behavior is required; done means a Cirq target accepts qir.v1 input in the same way.

Written by the indexing model from the issue text.

Description

Feature Request: It would be great if we could extend the azure.quantum.cirq.targets.Target with a QirTarget (or similar) sub-class that supports the qir.v1 input data format in the same way that the azure.quantum.qiskit.backends.AzureBackendBase is extended by the AzureQirBackend

Dominant language
Python
Stars
160
Forks
113
Avg merge
6d 23h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/azure-quantum-python

All issues in microsoft/azure-quantum-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.