Skip to content
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

Update openqaoa-qiskit to Qiskit 1.0 #304

Closed
KilianPoirier opened this issue Apr 22, 2024 · 1 comment · May be fixed by #312
Closed

Update openqaoa-qiskit to Qiskit 1.0 #304

KilianPoirier opened this issue Apr 22, 2024 · 1 comment · May be fixed by #312
Assignees

Comments

@KilianPoirier
Copy link
Collaborator

Issue Description

OpenQAOA is currently not compatible with the latest major release of Qiskit 1.0 and above, for more details see Qiskit release notes.

It is important that we update the package requirements and migrate to this new release before the anterior version becomes obsolete and support from the IBM backends stop for older versions of the package.

This issue concerns mostly the Qiskit plugin (openqaoa-qiskit) but also has implications on the Azure plugin (openqaoa-azure) because of its dependencies.

Changes to be made

  • Update Qiskit dependencies in openqaoa-qiskit to be compatible with the latest major release. More details can be found in the release notes and the migration guide provided by IBM. Changes include:
    • Repackaging of the qiskit package. qiskit-terra has been removed and the core of the package is now located in qiskit itself. qiskit-aer now has to be imported on its own.
    • Update of the primitives features.
    • QASM conversion methods have been removed.
  • Update Qiskit dependencies in openqaoa-azure if needed. Currently the version of Qiskit in the Azure quantum package is limited to <1.0 but it may be updated in the near future.
@KilianPoirier KilianPoirier changed the title Update openqaoa-qiskit to Qiskit 1.0 Update openqaoa-qiskit to Qiskit 1.0 Apr 22, 2024
@prakharb10
Copy link

Submitted #312 as a possible fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants