[FEATURE] Require openqasm3 1.0.2 and a fixed openpulse after openpulse-python#44 ships
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 35/100
- Issue 类型
- 重构
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, python
- 领域
- build-system, release, testing
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
openpulserelease with that fix is on PyPI. - That release passes pyqasm's pulse tests with
openqasm31.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 theinspectprobe and_PARSE_KWARGS. Callopenqasm3.parse(program, ignore_version=True)directly.- The
Test against openqasm3 1.0.1CI job and.github/requirements/openqasm3-1.0.1.{in,txt}. - The code path that handles
nopas a gate call, which only older parsers produce. - Test markers that skip on older
openqasm3, such ashasattr(QuantumNop)and the measurement-call skip. - The 1.0.1 wording in the
describe_parse_errordocstring. Keep its token-first order: 1.0.2 raises"parse failed"for every syntax error.
Remove the openpulse workaround:
- The
ValidationErrorthat names openpulse 1.0.1 with openqasm3 1.0.2. - The skip and xfail markers on assignments in
calblocks. Those tests must pass.
Add a CHANGELOG entry.
Completed when:
tox -e unit-testspasses withopenqasm3==1.0.2and the newopenpulse, with no version-gated skips left.grep -rn "1\.0\.1" src tests .githubfinds noopenqasm3oropenpulsecompatibility code.- An
OPENQASM 2.0program and adefcalwith an assignment both load.
Related: qBraid/qBraid#1554 caps openqasm3<1.0.2 in the SDK until a pyqasm release passes ignore_version=True.
- 主要语言
- Python
- 星标
- 29
- 派生
- 33
- 平均合并
- 1 天 3 小时
- 30 天内合并 PR
- 14
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
qBraid/pyqasm 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
[FEATURE] Drop Python 3.10 and add Python 3.15可能已有人在做 @TheGupta2012 今天认领。 未关闭enhancement
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
enhancement error-handling program-validation
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
Integer division for casts, int array elements, bitwise results, ** and int-returning subroutines未关闭
难度 3/5 1-2 天 新手友好度 52/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 2 天内回复
-
[Bug]: LANGSMITH_SAMPLING_RATE ignores fractional values (isdigit check), traces 100% of requests未关闭
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
platform/backend tests
难度 2/5 1-3 小时 新手友好度 78/100
Significant-Gravitas/AutoGPT#17100 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
MervinPraison/PraisonAI#6710 · 1 条评论 ·
维护者通常 1 天内回复
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 64/100