• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Qiskit / qiskit / 26520813064 / 1
88%
main: 88%

Build:
DEFAULT BRANCH: main
Ran 27 May 2026 03:58PM UTC
Files 944
Run time 50s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

27 May 2026 02:48PM UTC coverage: 87.61% (-0.002%) from 87.612%
26520813064.1

push

github

web-flow
Use public `qiskit.circuit` APIs in `qiskit.synthesis` (#16253)

* Use public `qiskit.circuit` APIs in `qiskit.synthesis`

We have a long-standing problem of `qiskit.circuit` reversing the module
hierarchy and including import-time imports of `qiskit.synthesis`.  The
synthesis module is supposed to be higher level than `circuit`, and only
used to provide the "default" (`Instruction.definition`) syntheses of
various library objects.  Those imports should be done at runtime of the
`_define` methods.

This ensures that `qiskit.synthesis` is only using `qiskit.circuit` via
its public interface, which is how the module API-boundary separation is
supposed to work.  This is a little more code churn than is ideal, but
my hope is that this is a good stepping stone along the way to properly
fixing the import structure of Qiskit, and that now `synthesis`'s
imports look right everywhere, any new files will copy the correct
style.

I've done the same for `qiskit.quantum_info` where possible, but there's
a couple of places that are using items that _aren't_ publicly exported
(`operators.predicates` is a big one, and might be an oversight in the
`qiskit.quantum_info` module).

* Remove unused import

108599 of 123957 relevant lines covered (87.61%)

961990.24 hits per line

Source Files on job 26520813064.1
  • Tree
  • List 944
  • Changed 38
  • Source Changed 35
  • Coverage Changed 30
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 26520813064
  • f0fae6f3 on github
  • Prev Job for on main (#26508690579.1)
  • Next Job for on main (#26522538851.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc