-
Notifications
You must be signed in to change notification settings - Fork 85
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 new FAQ about metapackage and include install snippets to intro #2516
base: main
Are you sure you want to change the base?
Conversation
One or more of the following people are relevant to this code: |
@@ -38,6 +38,14 @@ Example of citing IBM Quantum Composer: | |||
|
|||
> IBM Quantum Composer. 2023. url: https://<span>quantum.ibm.com/composer</span> | |||
|
|||
## What happened to Qiskit Aer, Qiskit Nature, Qiskit Experiments, etc.? |
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.
## What happened to Qiskit Aer, Qiskit Nature, Qiskit Experiments, etc.? | |
## What happened to Python distributions such as Qiskit Aer, Qiskit Nature, and Qiskit Experiments? |
@@ -38,6 +38,14 @@ Example of citing IBM Quantum Composer: | |||
|
|||
> IBM Quantum Composer. 2023. url: https://<span>quantum.ibm.com/composer</span> | |||
|
|||
## What happened to Qiskit Aer, Qiskit Nature, Qiskit Experiments, etc.? | |||
|
|||
Before the release of the Qiskit SDK v1.0, Qiskit was comprised of many different Python distributions such as: `qiskit-terra`, the compiler core; `qiskit-aer`, the high-performance simulator; the original IBM Quantum™ provider; and several now-obsolete packages providing particular exploratory algorithmic or experiment-running features. |
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.
Before the release of the Qiskit SDK v1.0, Qiskit was comprised of many different Python distributions such as: `qiskit-terra`, the compiler core; `qiskit-aer`, the high-performance simulator; the original IBM Quantum™ provider; and several now-obsolete packages providing particular exploratory algorithmic or experiment-running features. | |
Before the release of the Qiskit SDK v1.0, Qiskit was comprised of many different Python distributions, such as `qiskit-terra`, the compiler core; `qiskit-aer`, the high-performance simulator; the original IBM Quantum™ provider; and several now-obsolete packages providing particular exploratory algorithmic or experiment-running features. |
|
||
Before the release of the Qiskit SDK v1.0, Qiskit was comprised of many different Python distributions such as: `qiskit-terra`, the compiler core; `qiskit-aer`, the high-performance simulator; the original IBM Quantum™ provider; and several now-obsolete packages providing particular exploratory algorithmic or experiment-running features. | ||
|
||
These separate software packages were combined together into what was called the Qiskit *metapackage* which allowed users to install all of these components together through `pip install qiskit`. This metapackage architecture was removed with the release of the Qiskit SDK v1.0 and each of the individual software distributions need to be installed separately. |
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.
These separate software packages were combined together into what was called the Qiskit *metapackage* which allowed users to install all of these components together through `pip install qiskit`. This metapackage architecture was removed with the release of the Qiskit SDK v1.0 and each of the individual software distributions need to be installed separately. | |
These separate software packages were combined into what was called the Qiskit *metapackage*, which allowed users to install all of these components together through `pip install qiskit`. This metapackage architecture was removed with the release of the Qiskit SDK v1.0, and now each of the individual software distributions need to be installed separately. |
|
||
These separate software packages were combined together into what was called the Qiskit *metapackage* which allowed users to install all of these components together through `pip install qiskit`. This metapackage architecture was removed with the release of the Qiskit SDK v1.0 and each of the individual software distributions need to be installed separately. | ||
|
||
Check out the [Qiskit ecosystem](https://www.ibm.com/quantum/ecosystem) to find the package you may be looking for. You can also read the [1.0 migration guide](./migration-guides/qiskit-1.0-installation#why-these-changes-happened) for more information about why this change happened. |
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.
Check out the [Qiskit ecosystem](https://www.ibm.com/quantum/ecosystem) to find the package you may be looking for. You can also read the [1.0 migration guide](./migration-guides/qiskit-1.0-installation#why-these-changes-happened) for more information about why this change happened. | |
Visit the [Qiskit ecosystem](https://www.ibm.com/quantum/ecosystem) to find the package to suit your needs. You can also read the [v1.0 migration guide](/migration-guides/qiskit-1.0-installation#why-these-changes-happened) for more information about this change. |
Closes #2486 and closes #2488