-
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
Deprecate warning box in docs #8600
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:
|
Pull Request Test Coverage Report for Build 4005589012
💛 - Coveralls |
Can you post a screenshot of how this will show up in the docs? |
e8b63ae
to
2dd1af7
Compare
From @kdk:
Because of Qiskit/qiskit_sphinx_theme#71, the current look is not the best. |
On hold, since |
|
…a into deprecate_docstrings
While we all agree with the final result. This implementation penalises import time and requiere a parser (either "in-house" or a dependency). So new plan is:
|
Closing this in favor of #9616 |
Summary
Following #1592, this PR extend
deprecate_arguments
anddeprecate_function
so they add a deprecation box note in the docstring.