-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Deprecate 2-argument callable for atomic_evolution
parameter
#13603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
One or more of the following people are relevant to this code:
|
The failing builds are no longer available, but maybe there's still a test using the deprecated signature, causing the CI to fail 🤔 |
Broken CI reminder! The button to update branch seems to have disappeared? But I would recommend doing so to assess the state of the PR :) |
test updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Is this a removal we'd like to apply in 2.0 or do we prefer to emit the warning throughout the 2.x series?
+1 for remove since I don't believe this is used much and it would simplify our lives 🙂 |
Alright. I added an issue to the 2.0 milestone to make sure we don't forget to do it. |
atomic_evolution
atomic_evolution
parameter
Summary
Following up #12724, the
PendingDeprecationWarning
there are now moved toDeprecationWarning
Details and comments
The argument
atomic_evolution
in the constructor for the classesLieTrotter
,ProductFormula
, andSuzukiTrotter
is a callable with a different signature now: fromCallable[[Pauli | SparsePauliOp, float], QuantumCircuit]
toCallable[[QuantumCircuit, Pauli | SparsePauliOp, float], None]
.