-
Notifications
You must be signed in to change notification settings - Fork 31
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
Deprecate CutQC #527
Deprecate CutQC #527
Conversation
Pull Request Test Coverage Report for Build 8560529644Details
💛 - Coveralls |
I put 0.8.0 as the release when cutqc will be removed. Don't know if we do micro releases and whether this should have been 0.7.1 instead. |
Co-authored-by: Jim Garrison <[email protected]>
Co-authored-by: Jim Garrison <[email protected]>
Following semantic versioning, we should not remove code in a patchlevel release. We only do it in a minor release because we are pre-1.0. So yes, 0.8.0 is indeed the soonest we should do the removal. |
Should we do a single deprecation at the |
As Jim pointed out to me, the norm in qiskit tends to be to do both (cf. files here), which is why I was inclined to do this here. |
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.
We need a release note. We can be a little more explanatory here about the migration.
@@ -275,7 +275,7 @@ | |||
"name": "python", | |||
"nbconvert_exporter": "python", | |||
"pygments_lexer": "ipython3", | |||
"version": "3.8.16" | |||
"version": "3.9.6" |
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.
Can probably restore this file from main and remove it from the diff here
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.
This is not actually resolved, but I won't hold up this PR for this.
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.
Sorry, should be good now: 2d2c553
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.
This all looks good to me. Thanks!
Co-authored-by: Jim Garrison <[email protected]>
Otherwise, a deprecation warning will show any time the tests are run
Otherwise we see the following when we run tests ``` circuit_knitting/utils/metrics.py::circuit_knitting.utils.metrics.cross_entropy <doctest circuit_knitting.utils.metrics.cross_entropy[0]>:1: DeprecationWarning: The function ``circuit_knitting.utils.metrics.cross_entropy()`` is deprecated as of circuit-knitting-toolbox 0.7.0. It will be removed Circuit knitting toolbox 0.8.0 release. circuit_knitting/utils/metrics.py::circuit_knitting.utils.metrics.MSE <doctest circuit_knitting.utils.metrics.MSE[0]>:1: DeprecationWarning: The function ``circuit_knitting.utils.metrics.MSE()`` is deprecated as of circuit-knitting-toolbox 0.7.0. It will be removed Circuit knitting toolbox 0.8.0 release. circuit_knitting/utils/metrics.py::circuit_knitting.utils.metrics.MAPE <doctest circuit_knitting.utils.metrics.MAPE[0]>:1: DeprecationWarning: The function ``circuit_knitting.utils.metrics.MAPE()`` is deprecated as of circuit-knitting-toolbox 0.7.0. It will be removed Circuit knitting toolbox 0.8.0 release. circuit_knitting/utils/metrics.py::circuit_knitting.utils.metrics.chi2_distance <doctest circuit_knitting.utils.metrics.chi2_distance[0]>:1: DeprecationWarning: The function ``circuit_knitting.utils.metrics.chi2_distance()`` is deprecated as of circuit-knitting-toolbox 0.7.0. It will be removed Circuit knitting toolbox 0.8.0 release. circuit_knitting/utils/metrics.py::circuit_knitting.utils.metrics.chi2_distance <doctest circuit_knitting.utils.metrics.chi2_distance[1]>:1: DeprecationWarning: The function ``circuit_knitting.utils.metrics.chi2_distance()`` is deprecated as of circuit-knitting-toolbox 0.7.0. It will be removed Circuit knitting toolbox 0.8.0 release. circuit_knitting/utils/metrics.py::circuit_knitting.utils.metrics.HOP <doctest circuit_knitting.utils.metrics.HOP[0]>:1: DeprecationWarning: The function ``circuit_knitting.utils.metrics.HOP()`` is deprecated as of circuit-knitting-toolbox 0.7.0. It will be removed Circuit knitting toolbox 0.8.0 release. ```
Otherwise, we will see a deprecation warning
Co-authored-by: Jim Garrison <[email protected]>
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, this looks great
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 again!
Now that automated cut finding has been introduced (#520), we can go ahead and deprecate CutQC (#494).