-
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
Remove execute() function #11565
Remove execute() function #11565
Conversation
One or more of the the following people are requested to review 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.
LGTM (once the lint/docs complaints are fixed). I anticipate some conflicts with #11422 just because we modify the same files, but they should be relatively easy to handle.
@@ -11,10 +11,10 @@ | |||
# that they have been altered from the originals. | |||
|
|||
""" | |||
Example showing how to use Qiskit-Terra at level 0 (novice). | |||
Example showing how to use Qiskit at level 0 (no optimization). |
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.
I don't think that "level 0" referred to the optimization level, I think that this was intended as a beginner-level example (maybe remove the mention to level 0 altogether?)
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.
oooohh... that totally makes sense. I changed for how to use Qiskit at introduction level.
in 2821c48
Co-authored-by: Elena Peña Tapia <[email protected]>
…rra into remove/execute/11044/1
Pull Request Test Coverage Report for Build 7638982603Warning: This coverage report may be inaccurate.We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
💛 - Coveralls |
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.
Happy to re-approve once the merge conflict is fixed.
@1ucian0 checking the docs build logs, I've realized that the API docs entry for execute needs to be removed too, that is |
good catch! fixing it in 7c5fc5e |
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.
I looks like the docs build has finally succeeded. Let's hope that there are no further surprises.
This reference to `transpile` was mistakenly inserted as part of 1a027ac (Qiskitgh-11565); `execute` used to ignore the `transpile` step for `Schedule`/`ScheduleBlock` and submit directly to `backend.run`. I am not clear if there are actually any backends that *accept* pulse jobs anymore, but if there are, this is what the text should have been translated to.
* Remove reference to `transpile` from Pulse docs This reference to `transpile` was mistakenly inserted as part of 1a027ac (gh-11565); `execute` used to ignore the `transpile` step for `Schedule`/`ScheduleBlock` and submit directly to `backend.run`. I am not clear if there are actually any backends that *accept* pulse jobs anymore, but if there are, this is what the text should have been translated to. * Update qiskit/pulse/builder.py Co-authored-by: Will Shanks <[email protected]> --------- Co-authored-by: Will Shanks <[email protected]>
* Remove reference to `transpile` from Pulse docs This reference to `transpile` was mistakenly inserted as part of 1a027ac (gh-11565); `execute` used to ignore the `transpile` step for `Schedule`/`ScheduleBlock` and submit directly to `backend.run`. I am not clear if there are actually any backends that *accept* pulse jobs anymore, but if there are, this is what the text should have been translated to. * Update qiskit/pulse/builder.py Co-authored-by: Will Shanks <[email protected]> --------- Co-authored-by: Will Shanks <[email protected]> (cherry picked from commit 8e3218b)
* Remove reference to `transpile` from Pulse docs This reference to `transpile` was mistakenly inserted as part of 1a027ac (gh-11565); `execute` used to ignore the `transpile` step for `Schedule`/`ScheduleBlock` and submit directly to `backend.run`. I am not clear if there are actually any backends that *accept* pulse jobs anymore, but if there are, this is what the text should have been translated to. * Update qiskit/pulse/builder.py Co-authored-by: Will Shanks <[email protected]> --------- Co-authored-by: Will Shanks <[email protected]> (cherry picked from commit 8e3218b) Co-authored-by: Jake Lishman <[email protected]>
* Remove reference to `transpile` from Pulse docs This reference to `transpile` was mistakenly inserted as part of 1a027ac (Qiskitgh-11565); `execute` used to ignore the `transpile` step for `Schedule`/`ScheduleBlock` and submit directly to `backend.run`. I am not clear if there are actually any backends that *accept* pulse jobs anymore, but if there are, this is what the text should have been translated to. * Update qiskit/pulse/builder.py Co-authored-by: Will Shanks <[email protected]> --------- Co-authored-by: Will Shanks <[email protected]>
Summary
Removal of
execute
which was deprecated in 0.46 #11044