-
Notifications
You must be signed in to change notification settings - Fork 88
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
Add to backend.run migration guide for 3rd party provider #2543
Comments
Because I'm too lazy to open another issue, it'd be great to also add the motivation behind the move to primitives (also described in #2496) to the overview page. |
closing in favor of #2469 |
@Eric-Arellano I think this issue is different from #2469. This one is about updating the content of the existing migration guide related to 3rd party provider (target audience being regular users). #2469 is about creating a new migration guide for 3rd party providers (target audience being providers). Sure you can do both in a single PR, but they don't have to be. |
I think this is all addressed in #2496 |
URL, if applicable
https://docs.quantum.ibm.com/migration-guides/qiskit-runtime
Describe the new content you are requesting.
Prompted by #2496 (comment), it'd be great to have a section on
Migrate from third party provider
underMigrate from backend.run to primitives
to show people how to migrate to primitives even if the 3rd party provider they use don't support primitives (i.e. via backend primitives). This would allow users to switch between Qiskit Runtime and other 3rd party providers with little code modification.If this new content request is accepted, do you want to write the content?
I can help the team by providing enough information to write the material
The text was updated successfully, but these errors were encountered: