-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Start deprecating pass_operations_over for PauliString and PauliStringPhasor #7294
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
ffe2b94
to
1d14cbe
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7294 +/- ##
==========================================
- Coverage 98.67% 98.67% -0.01%
==========================================
Files 1109 1109
Lines 96826 96713 -113
==========================================
- Hits 95543 95430 -113
Misses 1283 1283 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Hi reviewers, I intended to deprecate the class function in the PR as
The deprecating timeline is from v1.5 (starts warning) -> v2.0 (fully remove). Wonder if this matches the general deprecating process of Cirq. |
@Strilanc @NoureldinYosri @pavoljuhas wonder if you could help review this pr? this is part of #6946 |
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.
thanks @babacry for doing this and for keeping our code healthy
…ngPhasor (quantumlib#7294) * Starts deprecating pass_operations_over * use cirq._compat.deprecate * Fix usages in contrib/paulistring * fix lint * instruct coverage to ignore the deprecated funcs
Starts deprecating all pass_operations_over().
pass_operations_over class function for PauliString* Classes is supposed to be replaced by conjuaged_by(), after(), before(). And the function itself is confusing and misleading in terms of the input order (see #2351).
Context: #7123 and #2351.