You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do not raise deprecation warnings for internal uses of dag.duration and dag.unit (backport Qiskit#14133) (Qiskit#14147)
* Do not raise deprecation warnings for internal uses of dag.duration and dag.unit (Qiskit#14133)
* Filter Rust deprecation warning when calling dag.duration/dag.unit internally
Filter Rust deprecation warning when calling dag.duration/dag.unit internally
* Apply Matt's suggestions:
* Refactor access patterns: add dag._duration and dag._unit
* Refactor internal uses of dag.duration and dag.unit to rely on internal methods
* Remove blanket warning filters from unit test config
On top of these:
* Extend deprecation warnings to dag.duration and dag.unit setters (previously only in getters)
* Clean up unit test config from old filters
* Change stacklevel
* Fix circuit_to_dag
* Handle failing tests
* _DAGDependencyV2 is private and not a DAGCircuit, so don't use internal attributes
* Reduce duplication in getters and setters
(cherry picked from commit d0aa100)
# Conflicts:
# crates/circuit/src/dag_circuit.rs
# qiskit/transpiler/passes/scheduling/padding/base_padding.py
# test/python/circuit/test_scheduled_circuit.py
# test/python/compiler/test_transpiler.py
# test/utils/base.py
* Fix merge conflicts
* Address failing tests
* More fixes
* More fixes
* Last try
---------
Co-authored-by: Elena Peña Tapia <57907331+ElePT@users.noreply.github.com>
Co-authored-by: Elena Peña Tapia <epenatap@gmail.com>
0 commit comments