Qiskit / qiskit
88%
main: 88%

LAST BUILD BRANCH: stable/1.4
DEFAULT BRANCH: main
Repo Added
Files 916
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

LAST BUILD ON BRANCH gh-readonly-queue/main/pr-14589-3c811fe055f375eb78c6abc67fee3bedc738a51c
branch: gh-readonly-queue/main/pr-14589-3c811fe055f375eb78c6abc67fee3bedc738a51c
CHANGE BRANCH
x

coverage: 87.764% (-0.04%) from 87.807%
16121459629

push

github

web-flow 
Avoid py token usage in the common path for circuit_to_dag (#14589)

* Avoid py token usage in the common path for circuit_to_data

This commit adjusts the Python usage in the
DAGCircuit::from_circuit_data code paths. Most of the data model is in
Rust at this point with the exception of things explicitly defined in
Python (ie a custom gate in Python), ParameterExpression, and control
flow. While the latter two are in progress (see #13267 and #13271) we
don't need to block the development of C API features that depend on
circuit->dag conversion. The Python usage in this code path is around
parameterized global phase and deepcopying custom python gates.
Neither of these are possible from C because they're in Python and not
exposed to C. This commit removes the py token from the function
signatures and actively acquires the gil inline if we're using Python
parts of the data model when they're needed.

* Move deepcopy Python usage up to Python defined types

In the previous commit the py token acquisition was moved down into the
PackedInstruction::py_deepcopy() method instead of being the
responsibility of the caller. This decision was made because we only
need the py token in a context where objects defined in Python are
encountered. The goal of hiding the py token is that in a context
without python at all (i.e. the standalone C API) nothing callable from
a pure rust context requires the py token. The token was moved down so
that we only ever try to acquire the GIL in contexts where we have a
python defined object. The method only ever uses it to deep copy in the
case of PackedInstruction containing a Python defined object.

In code review the concern was raised that deepcopy is a purely python
construct and the `py_deepcopy` should very explicitly be the caller's
responsibility to assert they have the GIL by passing the py token. To
address this concern but also enable a Python free path through circuit
to dag conversion this commit moves the `deepcopy... (continued)

105 of 128 new or added lines in 11 files covered. (82.03%)

25 existing lines in 3 files now uncovered.

81048 of 92348 relevant lines covered (87.76%)

503807.5 hits per line

Relevant lines Covered
92348 RELEVANT LINES 81048 COVERED LINES
503807.5 HITS PER LINE
Source Files on gh-readonly-queue/main/pr-14589-3c811fe055f375eb78c6abc67fee3bedc738a51c

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
16121459629 gh-readonly-queue/main/pr-14589-3c811fe055f375eb78c6abc67fee3bedc738a51c Avoid py token usage in the common path for circuit_to_dag (#14589) * Avoid py token usage in the common path for circuit_to_data This commit adjusts the Python usage in the DAGCircuit::from_circuit_data code paths. Most of the data model is in ... push web-flow github
87.76
See All Builds (14015)