-
Notifications
You must be signed in to change notification settings - Fork 603
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
Raise DeprecationWarning only when the qasm code contains measurements #5904
Conversation
[sc-66318] |
Hello. You may have forgotten to update the changelog!
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## v0.37.0-rc0 #5904 +/- ##
==============================================
Coverage ? 99.66%
==============================================
Files ? 425
Lines ? 40458
Branches ? 0
==============================================
Hits ? 40324
Misses ? 134
Partials ? 0 ☔ View full report in Codecov by Sentry. |
Interesting branch name! |
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.
Looks good, thanks @astralcai :) May I ask for a test that no warning is raised for the no-measurements case? And maybe could add the PR number to the existing changelog entry, and a specification of the deprecationwarning being raised to deprecations.rst
?
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 @astralcai
Context:
#5882 led to deprecation warnings raised in non-applicable scenarios
Description of the Change:
Only raise deprecation warning if the circuit contains measurements
Benefits:
Less confusing deprecation warnings