-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[wip] Better handle pending deprecations #9601
Conversation
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
…nding-deprecation
Hm, looks like So, the This PR was the first of several improvements I was hoping to make in service of #8600. I'll mark this as WIP and regroup. Sorry for the noise! |
Pull Request Test Coverage Report for Build 4195565630
💛 - Coveralls |
As you noted we use the deprecation util in the application repos as well. I will also point out that the set of changes done by this PR, around the algorithms, is also changed by #9532 which is intended for the next release. |
Thanks for that context, @woodsp-ibm. @manoelmarques and I DMed about their two open PRs - I'm going to put up soon a prework PR that builds off of their |
Summary
Our deprecation policy distinguishes between
DeprecationWarning
vsPendingDeprecationWarning
: https://github.com/Qiskit/qiskit/blob/82810146c5061fad17c041e7e66196f92466ec1a/docs/deprecation_policy.rst#removing-a-featureThis PR improves support for
PendingDeprecationWarning
:deprecate_arguments
to clarify when something is pending.category: type
, which was unbounded to be the whole universe of Python types. When in reality, we only expected it to be eitherDeprecationWarning
orPendingDeprecationWarning
.pending={False,True}
makes clear this reality. It will help in future changes (like Deprecate warning box in docs #8600) to conditionally handle pending vs deprecated.Details and comments
This is prework for the rework ofchttps://github.com//pull/8600. I want to make sure our docs properly support
PendingDeprecationWarning
.