[FEATURE] Require openqasm3 1.0.2 and a fixed openpulse after openpulse-python#44 ships

Ouverte
#481 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
35/100
Type d'issue
Refactorisation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github-actions, python

Piste de recherche

Read pyproject.toml for the current openqasm3 and openpulse floors, then src/pyqasm/entrypoint.py for the 1.0.1 inspect/_PARSE_KWARGS probe and describe_parse_error wording. The removal also spans the openqasm3 1.0.1 CI job, .github/requirements/openqasm3-1.0.1.*, nop handling, and version-gated test markers. Do not start until #475 is merged, openpulse-python#44 ships, and the new openpulse passes pulse tests with openqasm3 1.0.2; finish with tox -e unit-tests and the grep check from the issue.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

dependencies enhancement
Feature Description

Raise pyqasm's floors to openqasm3 1.0.2 and to the first openpulse release that works with it. Then remove the 1.0.1 compatibility code.

Why this waits. openqasm3 1.0.2 broke loads() (#472). #475 restores support and keeps 1.0.1 working. pyqasm cannot require 1.0.2 yet. openpulse 1.0.1 bundles an older qasm3 grammar. With openqasm3 1.0.2 it fails on any assignment in a cal or defcal block (openqasm/openpulse-python#42). The upstream fix is openqasm/openpulse-python#44, still open.

Start when all of these hold:

  • #475 is merged and main CI is green.
  • openqasm/openpulse-python#44 is merged.
  • A new openpulse release with that fix is on PyPI.
  • That release passes pyqasm's pulse tests with openqasm3 1.0.2, with no skip or xfail markers.
Implementation (Optional)

Version bump in pyproject.toml:

  • openqasm3[parser]>=1.0.2,<2.0.0 (today >=1.0.0,<2.0.0).
  • pulse = ["openpulse>=<fixed release>"] (today >=1.0.1).

Remove the 1.0.1 compatibility added in #475:

  • src/pyqasm/entrypoint.py: drop the inspect probe and _PARSE_KWARGS. Call openqasm3.parse(program, ignore_version=True) directly.
  • The Test against openqasm3 1.0.1 CI job and .github/requirements/openqasm3-1.0.1.{in,txt}.
  • The code path that handles nop as a gate call, which only older parsers produce.
  • Test markers that skip on older openqasm3, such as hasattr(QuantumNop) and the measurement-call skip.
  • The 1.0.1 wording in the describe_parse_error docstring. Keep its token-first order: 1.0.2 raises "parse failed" for every syntax error.

Remove the openpulse workaround:

  • The ValidationError that names openpulse 1.0.1 with openqasm3 1.0.2.
  • The skip and xfail markers on assignments in cal blocks. Those tests must pass.

Add a CHANGELOG entry.

Completed when:

  • tox -e unit-tests passes with openqasm3==1.0.2 and the new openpulse, with no version-gated skips left.
  • grep -rn "1\.0\.1" src tests .github finds no openqasm3 or openpulse compatibility code.
  • An OPENQASM 2.0 program and a defcal with an assignment both load.

Related: qBraid/qBraid#1554 caps openqasm3<1.0.2 in the SDK until a pyqasm release passes ignore_version=True.

Langage dominant
Python
Étoiles
29
Forks
33
Merge moyen
1 j 3 h
PR mergées (30 j)
14

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de qBraid/pyqasm

Toutes les issues de qBraid/pyqasm

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.