# Qiskit IBM Quantum Provider (_NOW DEPRECATED_)
[![License](https://img.shields.io/github/license/Qiskit/qiskit-ibmq-provider.svg?style=popout-square)](https://opensource.org/licenses/Apache-2.0)[![Build Status](https://img.shields.io/travis/com/Qiskit/qiskit-ibmq-provider/master.svg?style=popout-square)](https://travis-ci.com/Qiskit/qiskit-ibmq-provider)[![](https://img.shields.io/github/release/Qiskit/qiskit-ibmq-provider.svg?style=popout-square)](https://github.com/Qiskit/qiskit-ibmq-provider/releases)[![](https://img.shields.io/pypi/dm/qiskit-ibmq-provider.svg?style=popout-square)](https://pypi.org/project/qiskit-ibmq-provider/)
---
**_PLEASE NOTE:_** _As of version 0.20.0, released in January 2023, `qiskit-ibmq-provider` has been deprecated
with its support ending and eventual archival being no sooner than 3 months from that date. The
function provided by `qiskit-ibmq-provider` is not going away rather it has being split out to separate repositories.
Please see the [Migration Guides](#migration-guides) section below for more detail. We encourage you
to migrate over at your earliest convenience._
---
**Qiskit** is an open-source SDK for working with quantum computers at the level of circuits, algorithms, and application modules.
This module contains a provider that allows accessing the **[IBM Quantum]**
systems and simulators.
## Migration Guides
All the functionality that `qiskit-ibmq-provider` provides has been migrated to other packages:
| Formerly | Current package | Details | Migration Guide |
| :---: | :---: | :---: | :---: |
| [`qiskit.providers.ibmq.experiment`](https://qiskit.org/documentation/apidoc/ibmq_experiment.html) | [`qiskit-ibm-experiment`](https://pypi.org/project/qiskit-ibm-experiment/)<br>(no docs yet) | For the features related with the IBM Quantum experiment database service. | [guide](https://github.com/Qiskit/qiskit-ibm-experiment/blob/main/docs/tutorials/Migration%20Guide.ipynb) |
| [`qiskit.providers.ibmq.runtime`](https://qiskit.org/documentation/apidoc/ibmq_runtime.html) | [`qiskit-ibm-runtime`](https://pypi.org/project/qiskit-ibm-runtime/)<br>([docs](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/)) | Use this package if you prefer getting high quality probability distribution or expectation values without having to optimize the circuits or mitigate results yourself. | [guide](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/migrate_from_ibmq.html) |
| Rest of [`qiskit.providers.ibmq`](https://qiskit.org/documentation/apidoc/ibmq_provider.html) | [`qiskit-ibm-provider`](https://pypi.org/project/qiskit-ibm-provider)<br>([docs](https://qiskit.org/documentation/partners/qiskit_ibm_provider/)) | Use this package if you need direct access to the backends to do experiments like device characterization. | [guide](https://qiskit.org/documentation/partners/qiskit_ibm_provider/tutorials/Migration_Guide_from_qiskit-ibmq-provider.html) |
These packages can be installed by themselves (via the standard pip install command, e.g. ``pip install qiskit-ibm-provider``) and are not part of the Qiskit metapackage.
## Installation
We encourage installing Qiskit via the PIP tool (a python package manager),
which installs all Qiskit elements and components, including this one.
```bash
pip install qiskit
```
PIP will handle all dependencies automatically for us and you will always
install the latest (and well-tested) version.
To install from source, follow the instructions in the
[contribution guidelines].
## Setting up the IBM Quantum Provider
Once the package is installed, you can access the provider from Qiskit.
> **Note**: Since November 2019 (and with version `0.4` of this
> `qiskit-ibmq-provider` package / version `0.14` of the `qiskit` package)
> legacy Quantum Experience or QConsole (v1) accounts are no longer supported.
> If you are still using a v1 account, please follow the steps described in
> [update instructions](#updating-to-the-new-IBM-Quantum) to update your account.
### Configure your IBM Quantum credentials
1. Create an IBM Quantum account or log in to your existing account by visiting
the [IBM Quantum login page].
2. Copy (and/or optionally regenerate) your API token from your
[IBM Quantum account page].
3. Take your token from step 2, here called `MY_API_TOKEN`, and run:
```python
from qiskit import IBMQ
IBMQ.save_account('MY_API_TOKEN')
```
The command above stores your credentials locally in a configuration file called `qiskitrc`.
By default, this file is located in `$HOME/.qiskit`, where `$HOME` is your home directory. If
you are still using `Qconfig.py`, please delete that file and run the command above.
### Accessing your IBM Quantum backends
After calling `IBMQ.save_account()`, your credentials will be stored on disk.
Once they are stored, at any point in the future you can load and use them
in your program simply via:
```python
from qiskit import IBMQ
provider = IBMQ.load_account()
backend = provider.get_backend('ibmq_qasm_simulator')
```
Alternatively, if you do not want to save your credentials to disk and only
intend to use them during the current session, you can use:
```python
from qiskit import IBMQ
provider = IBMQ.enable_account('MY_API_TOKEN')
backend = provider.get_backend('ibmq_qasm_simulator')
```
By default, all IBM Quantum accounts have access to the same, open project
(hub: `ibm-q`, group: `open`, project: `main`). For convenience, the
`IBMQ.load_account()` and `IBMQ.enable_account()` methods will return a provider
for that project. If you have access to other projects, you can use:
```python
provider_2 = IBMQ.get_provider(hub='MY_HUB', group='MY_GROUP', project='MY_PROJECT')
```
## Updating to the new IBM Quantum
Since November 2019 (and with version `0.4` of this `qiskit-ibmq-provider`
package), the IBM Quantum Provider only supports the new [IBM Quantum], dropping
support for the legacy Quantum Experience and Qconsole accounts. The new IBM Quantum is also referred as `v2`, whereas the legacy one and Qconsole as `v1`.
This section includes instructions for updating your accounts and programs.
Please note that:
* the IBM Quantum Experience `v1` credentials and the programs written for pre-0.3
versions will still be working during the `0.3.x` series. From 0.4 onwards,
only `v2` credentials are supported, and it is recommended to upgrade
in order to take advantage of the new features.
* updating your credentials to the IBM Quantum `v2` implies that you
will need to update your programs. The sections below contain instructions
on how to perform the transition.
### Updating your IBM Quantum credentials
If you have credentials for the legacy Quantum Experience or Qconsole stored in
disk, you can make use of `IBMQ.update_account()` helper. This helper will read
your current credentials stored in disk and attempt to convert them:
```python
from qiskit import IBMQ
IBMQ.update_account()
```
```
Found 2 credentials.
The credentials stored will be replaced with a single entry with token "MYTOKEN"
and the new IBM Quantum v2 URL (https://auth.quantum-computing.ibm.com/api).
In order to access the provider, please use the new "IBMQ.get_provider()" methods:
provider0 = IBMQ.load_account()
provider1 = IBMQ.get_provider(hub='A', group='B', project='C')
Note you need to update your programs in order to retrieve backends from a
specific provider directly:
backends = provider0.backends()
backend = provider0.get_backend('ibmq_qasm_simulator')
Update the credentials? [y/N]
```
Upon confirmation, your credentials will be overwritten with a valid IBM Quantum
v2 set of credentials. For more complex cases, consider deleting your
previous credentials via `IBMQ.delete_accounts()` and follow the instructions
in the [IBM Quantum account page].
### Updating your programs
The new IBM Quantum support also introduces a more structured approach for accessing backends.
Previously, access to all backends was centralized through:
```python
IBMQ.backends()
IBMQ.get_backend('ibmq_qasm_simulator')
```
In version `0.3` onwards, the preferred way to access the backends is via a
`Provider` for one of your projects instead of via the global `IBMQ` instance
directly, allowing for more granular control over
the project you are using:
```python
my_provider = IBMQ.get_provider()
my_provider.backends()
my_provider.get_backend('ibmq_qasm_simulator')
```
In a similar spirit, you can check the providers that you have access to via:
```python
IBMQ.providers()
```
In addition, since the new IBM Quantum provides only one set of
credentials, the account management methods in IBMQ are now in singular form.
For example, you should use `IBMQ.load_account()` instead of
`IBMQ.load_accounts()`. An `IBMQAccountError` exception is raised if you
attempt to use the legacy methods with an IBM Quantum v2 account.
The following tables contains a quick reference for the differences between the
two versions. Please refer to the documentation of each method for more in
depth details:
### Account management
| <0.3 / v1 credentials | >=0.3 and v2 credentials |
| --- | --- |
| N/A | `IBMQ.update_account()` |
| `IBMQ.save_account(token, url)` | `IBMQ.save_account(token)`
| `IBMQ.load_accounts()` | `provider = IBMQ.load_account()`
| `IBMQ.enable_account()` | `provider = IBMQ.enable_account()`
| `IBMQ.disable_accounts()` | `IBMQ.disable_account()`
| `IBMQ.active_accounts()` | `IBMQ.active_account()`
| `IBMQ.stored_accounts()` | `IBMQ.stored_account()`
| `IBMQ.delete_accounts()` | `IBMQ.delete_account()`
### Using backends
| <0.3 / v1 credentials | >=0.3 and v2 credentials |
| --- | --- |
| N/A | `providers = IBMQ.providers()` |
| `backend = IBMQ.get_backend(name, hub='HUB')` | `provider = IBMQ.get_provider(hub='HUB')` |
| | `backend = provider.get_backend(name)` |
| `backends = IBMQ.backends(hub='HUB')` | `provider = IBMQ.get_provider(hub='HUB')` |
| | `backends = provider.backends()` |
## Contribution Guidelines
If you'd like to contribute to IBM Quantum Provider, please take a look at our
[contribution guidelines]. This project adheres to Qiskit's [code of conduct].
By participating, you are expect to uphold to this code.
We use [GitHub issues] for tracking requests and bugs. Please use our [slack]
for discussion and simple questions. To join our Slack community use the
invite link at [Qiskit.org]. For questions that are more suited for a forum we
use the `Qiskit` tag in [Stack Exchange].
## Next Steps
Now you're set up and ready to check out some of the other examples from our
[Qiskit Tutorial] repository.
## Authors and Citation
The Qiskit IBM Quantum Provider is the work of [many people] who contribute to the
project at different levels. If you use Qiskit, please cite as per the included
[BibTeX file].
## License
[Apache License 2.0].
[IBM Quantum]: https://quantum-computing.ibm.com
[IBM Quantum login page]: https://quantum-computing.ibm.com/login
[IBM Quantum account page]: https://quantum-computing.ibm.com/account
[contribution guidelines]: https://github.com/Qiskit/qiskit-ibmq-provider/blob/master/CONTRIBUTING.md
[code of conduct]: https://github.com/Qiskit/qiskit-ibmq-provider/blob/master/CODE_OF_CONDUCT.md
[GitHub issues]: https://github.com/Qiskit/qiskit-ibmq-provider/issues
[slack]: https://qiskit.slack.com
[Qiskit.org]: https://qiskit.org
[Stack Exchange]: https://quantumcomputing.stackexchange.com/questions/tagged/qiskit
[Qiskit Tutorial]: https://github.com/Qiskit/qiskit-tutorial
[many people]: https://github.com/Qiskit/qiskit-ibmq-provider/graphs/contributors
[BibTeX file]: https://github.com/Qiskit/qiskit/blob/master/Qiskit.bib
[Apache License 2.0]: https://github.com/Qiskit/qiskit-ibmq-provider/blob/master/LICENSE.txt
Raw data
{
"_id": null,
"home_page": "https://github.com/Qiskit/qiskit-ibmq-provider",
"name": "qiskit-ibmq-provider",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.7",
"maintainer_email": "",
"keywords": "qiskit sdk quantum api ibmq",
"author": "Qiskit Development Team",
"author_email": "hello@qiskit.org",
"download_url": "https://files.pythonhosted.org/packages/ed/27/f122ae1061eb2f06961181eaa5222fb91b53a4bc511354cdecdb71a9ce04/qiskit-ibmq-provider-0.20.2.tar.gz",
"platform": null,
"description": "# Qiskit IBM Quantum Provider (_NOW DEPRECATED_)\n\n[![License](https://img.shields.io/github/license/Qiskit/qiskit-ibmq-provider.svg?style=popout-square)](https://opensource.org/licenses/Apache-2.0)[![Build Status](https://img.shields.io/travis/com/Qiskit/qiskit-ibmq-provider/master.svg?style=popout-square)](https://travis-ci.com/Qiskit/qiskit-ibmq-provider)[![](https://img.shields.io/github/release/Qiskit/qiskit-ibmq-provider.svg?style=popout-square)](https://github.com/Qiskit/qiskit-ibmq-provider/releases)[![](https://img.shields.io/pypi/dm/qiskit-ibmq-provider.svg?style=popout-square)](https://pypi.org/project/qiskit-ibmq-provider/)\n\n---\n\n**_PLEASE NOTE:_** _As of version 0.20.0, released in January 2023, `qiskit-ibmq-provider` has been deprecated\nwith its support ending and eventual archival being no sooner than 3 months from that date. The\nfunction provided by `qiskit-ibmq-provider` is not going away rather it has being split out to separate repositories.\nPlease see the [Migration Guides](#migration-guides) section below for more detail. We encourage you\nto migrate over at your earliest convenience._\n\n---\n\n**Qiskit** is an open-source SDK for working with quantum computers at the level of circuits, algorithms, and application modules.\n\nThis module contains a provider that allows accessing the **[IBM Quantum]**\nsystems and simulators.\n\n## Migration Guides\n\n\nAll the functionality that `qiskit-ibmq-provider` provides has been migrated to other packages:\n\n| Formerly | Current package | Details | Migration Guide |\n| :---: | :---: | :---: | :---: |\n| [`qiskit.providers.ibmq.experiment`](https://qiskit.org/documentation/apidoc/ibmq_experiment.html) | [`qiskit-ibm-experiment`](https://pypi.org/project/qiskit-ibm-experiment/)<br>(no docs yet) | For the features related with the IBM Quantum experiment database service. | [guide](https://github.com/Qiskit/qiskit-ibm-experiment/blob/main/docs/tutorials/Migration%20Guide.ipynb) |\n| [`qiskit.providers.ibmq.runtime`](https://qiskit.org/documentation/apidoc/ibmq_runtime.html) | [`qiskit-ibm-runtime`](https://pypi.org/project/qiskit-ibm-runtime/)<br>([docs](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/)) | Use this package if you prefer getting high quality probability distribution or expectation values without having to optimize the circuits or mitigate results yourself. | [guide](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/migrate_from_ibmq.html) |\n| Rest of [`qiskit.providers.ibmq`](https://qiskit.org/documentation/apidoc/ibmq_provider.html) | [`qiskit-ibm-provider`](https://pypi.org/project/qiskit-ibm-provider)<br>([docs](https://qiskit.org/documentation/partners/qiskit_ibm_provider/)) | Use this package if you need direct access to the backends to do experiments like device characterization. | [guide](https://qiskit.org/documentation/partners/qiskit_ibm_provider/tutorials/Migration_Guide_from_qiskit-ibmq-provider.html) |\n\n\nThese packages can be installed by themselves (via the standard pip install command, e.g. ``pip install qiskit-ibm-provider``) and are not part of the Qiskit metapackage.\n\n\n## Installation\n\nWe encourage installing Qiskit via the PIP tool (a python package manager),\nwhich installs all Qiskit elements and components, including this one.\n\n```bash\npip install qiskit\n```\n\nPIP will handle all dependencies automatically for us and you will always\ninstall the latest (and well-tested) version.\n\nTo install from source, follow the instructions in the\n[contribution guidelines].\n\n## Setting up the IBM Quantum Provider\n\nOnce the package is installed, you can access the provider from Qiskit.\n\n> **Note**: Since November 2019 (and with version `0.4` of this\n> `qiskit-ibmq-provider` package / version `0.14` of the `qiskit` package)\n> legacy Quantum Experience or QConsole (v1) accounts are no longer supported.\n> If you are still using a v1 account, please follow the steps described in\n> [update instructions](#updating-to-the-new-IBM-Quantum) to update your account.\n\n### Configure your IBM Quantum credentials\n\n1. Create an IBM Quantum account or log in to your existing account by visiting\n the [IBM Quantum login page].\n\n2. Copy (and/or optionally regenerate) your API token from your\n [IBM Quantum account page].\n\n3. Take your token from step 2, here called `MY_API_TOKEN`, and run:\n\n ```python\n from qiskit import IBMQ\n IBMQ.save_account('MY_API_TOKEN')\n ```\n\n The command above stores your credentials locally in a configuration file called `qiskitrc`.\n By default, this file is located in `$HOME/.qiskit`, where `$HOME` is your home directory. If\n you are still using `Qconfig.py`, please delete that file and run the command above.\n\n### Accessing your IBM Quantum backends\n\nAfter calling `IBMQ.save_account()`, your credentials will be stored on disk.\nOnce they are stored, at any point in the future you can load and use them\nin your program simply via:\n\n```python\nfrom qiskit import IBMQ\n\nprovider = IBMQ.load_account()\nbackend = provider.get_backend('ibmq_qasm_simulator')\n```\n\nAlternatively, if you do not want to save your credentials to disk and only\nintend to use them during the current session, you can use:\n\n```python\nfrom qiskit import IBMQ\n\nprovider = IBMQ.enable_account('MY_API_TOKEN')\nbackend = provider.get_backend('ibmq_qasm_simulator')\n```\n\nBy default, all IBM Quantum accounts have access to the same, open project\n(hub: `ibm-q`, group: `open`, project: `main`). For convenience, the\n`IBMQ.load_account()` and `IBMQ.enable_account()` methods will return a provider\nfor that project. If you have access to other projects, you can use:\n\n```python\nprovider_2 = IBMQ.get_provider(hub='MY_HUB', group='MY_GROUP', project='MY_PROJECT')\n```\n\n## Updating to the new IBM Quantum\n\nSince November 2019 (and with version `0.4` of this `qiskit-ibmq-provider`\npackage), the IBM Quantum Provider only supports the new [IBM Quantum], dropping\nsupport for the legacy Quantum Experience and Qconsole accounts. The new IBM Quantum is also referred as `v2`, whereas the legacy one and Qconsole as `v1`.\n\nThis section includes instructions for updating your accounts and programs.\nPlease note that:\n * the IBM Quantum Experience `v1` credentials and the programs written for pre-0.3\n versions will still be working during the `0.3.x` series. From 0.4 onwards,\n only `v2` credentials are supported, and it is recommended to upgrade\n in order to take advantage of the new features.\n * updating your credentials to the IBM Quantum `v2` implies that you\n will need to update your programs. The sections below contain instructions\n on how to perform the transition.\n\n### Updating your IBM Quantum credentials\n\nIf you have credentials for the legacy Quantum Experience or Qconsole stored in\ndisk, you can make use of `IBMQ.update_account()` helper. This helper will read\nyour current credentials stored in disk and attempt to convert them:\n\n```python\nfrom qiskit import IBMQ\n\nIBMQ.update_account()\n```\n\n```\nFound 2 credentials.\nThe credentials stored will be replaced with a single entry with token \"MYTOKEN\"\nand the new IBM Quantum v2 URL (https://auth.quantum-computing.ibm.com/api).\n\nIn order to access the provider, please use the new \"IBMQ.get_provider()\" methods:\n\n provider0 = IBMQ.load_account()\n provider1 = IBMQ.get_provider(hub='A', group='B', project='C')\n\nNote you need to update your programs in order to retrieve backends from a\nspecific provider directly:\n\n backends = provider0.backends()\n backend = provider0.get_backend('ibmq_qasm_simulator')\n\nUpdate the credentials? [y/N]\n```\n\nUpon confirmation, your credentials will be overwritten with a valid IBM Quantum\nv2 set of credentials. For more complex cases, consider deleting your\nprevious credentials via `IBMQ.delete_accounts()` and follow the instructions\nin the [IBM Quantum account page].\n\n### Updating your programs\n\nThe new IBM Quantum support also introduces a more structured approach for accessing backends.\nPreviously, access to all backends was centralized through:\n\n```python\nIBMQ.backends()\nIBMQ.get_backend('ibmq_qasm_simulator')\n```\n\nIn version `0.3` onwards, the preferred way to access the backends is via a\n`Provider` for one of your projects instead of via the global `IBMQ` instance\ndirectly, allowing for more granular control over\nthe project you are using:\n\n```python\nmy_provider = IBMQ.get_provider()\nmy_provider.backends()\nmy_provider.get_backend('ibmq_qasm_simulator')\n```\n\nIn a similar spirit, you can check the providers that you have access to via:\n```python\nIBMQ.providers()\n```\n\nIn addition, since the new IBM Quantum provides only one set of\ncredentials, the account management methods in IBMQ are now in singular form.\nFor example, you should use `IBMQ.load_account()` instead of\n`IBMQ.load_accounts()`. An `IBMQAccountError` exception is raised if you\nattempt to use the legacy methods with an IBM Quantum v2 account.\n\nThe following tables contains a quick reference for the differences between the\ntwo versions. Please refer to the documentation of each method for more in\ndepth details:\n\n### Account management\n\n| <0.3 / v1 credentials | >=0.3 and v2 credentials |\n| --- | --- |\n| N/A | `IBMQ.update_account()` |\n| `IBMQ.save_account(token, url)` | `IBMQ.save_account(token)`\n| `IBMQ.load_accounts()` | `provider = IBMQ.load_account()`\n| `IBMQ.enable_account()` | `provider = IBMQ.enable_account()`\n| `IBMQ.disable_accounts()` | `IBMQ.disable_account()`\n| `IBMQ.active_accounts()` | `IBMQ.active_account()`\n| `IBMQ.stored_accounts()` | `IBMQ.stored_account()`\n| `IBMQ.delete_accounts()` | `IBMQ.delete_account()`\n\n### Using backends\n\n| <0.3 / v1 credentials | >=0.3 and v2 credentials |\n| --- | --- |\n| N/A | `providers = IBMQ.providers()` |\n| `backend = IBMQ.get_backend(name, hub='HUB')` | `provider = IBMQ.get_provider(hub='HUB')` |\n| | `backend = provider.get_backend(name)` |\n| `backends = IBMQ.backends(hub='HUB')` | `provider = IBMQ.get_provider(hub='HUB')` |\n| | `backends = provider.backends()` |\n\n\n## Contribution Guidelines\n\nIf you'd like to contribute to IBM Quantum Provider, please take a look at our\n[contribution guidelines]. This project adheres to Qiskit's [code of conduct].\nBy participating, you are expect to uphold to this code.\n\nWe use [GitHub issues] for tracking requests and bugs. Please use our [slack]\nfor discussion and simple questions. To join our Slack community use the\ninvite link at [Qiskit.org]. For questions that are more suited for a forum we\nuse the `Qiskit` tag in [Stack Exchange].\n\n## Next Steps\n\nNow you're set up and ready to check out some of the other examples from our\n[Qiskit Tutorial] repository.\n\n## Authors and Citation\n\nThe Qiskit IBM Quantum Provider is the work of [many people] who contribute to the\nproject at different levels. If you use Qiskit, please cite as per the included\n[BibTeX file].\n\n## License\n\n[Apache License 2.0].\n\n\n[IBM Quantum]: https://quantum-computing.ibm.com\n[IBM Quantum login page]: https://quantum-computing.ibm.com/login\n[IBM Quantum account page]: https://quantum-computing.ibm.com/account\n[contribution guidelines]: https://github.com/Qiskit/qiskit-ibmq-provider/blob/master/CONTRIBUTING.md\n[code of conduct]: https://github.com/Qiskit/qiskit-ibmq-provider/blob/master/CODE_OF_CONDUCT.md\n[GitHub issues]: https://github.com/Qiskit/qiskit-ibmq-provider/issues\n[slack]: https://qiskit.slack.com\n[Qiskit.org]: https://qiskit.org\n[Stack Exchange]: https://quantumcomputing.stackexchange.com/questions/tagged/qiskit\n[Qiskit Tutorial]: https://github.com/Qiskit/qiskit-tutorial\n[many people]: https://github.com/Qiskit/qiskit-ibmq-provider/graphs/contributors\n[BibTeX file]: https://github.com/Qiskit/qiskit/blob/master/Qiskit.bib\n[Apache License 2.0]: https://github.com/Qiskit/qiskit-ibmq-provider/blob/master/LICENSE.txt\n",
"bugtrack_url": null,
"license": "Apache 2.0",
"summary": "Qiskit provider for accessing the quantum devices and simulators at IBMQ",
"version": "0.20.2",
"project_urls": {
"Bug Tracker": "https://github.com/Qiskit/qiskit-ibmq-provider/issues",
"Documentation": "https://qiskit.org/documentation/",
"Homepage": "https://github.com/Qiskit/qiskit-ibmq-provider",
"Source Code": "https://github.com/Qiskit/qiskit-ibmq-provider"
},
"split_keywords": [
"qiskit",
"sdk",
"quantum",
"api",
"ibmq"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "a2adf0af9c18c198f8c6e29657bfa7b24c6cd0a8cd75b79ba2ba7d2a97585380",
"md5": "22da3a4828af245207646f09fbb126a8",
"sha256": "4f669b93f7d3d1e7b9439399cb1fa391083ea4ae81331f69d8269a9d4539b76a"
},
"downloads": -1,
"filename": "qiskit_ibmq_provider-0.20.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "22da3a4828af245207646f09fbb126a8",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.7",
"size": 241462,
"upload_time": "2023-03-07T19:03:11",
"upload_time_iso_8601": "2023-03-07T19:03:11.438972Z",
"url": "https://files.pythonhosted.org/packages/a2/ad/f0af9c18c198f8c6e29657bfa7b24c6cd0a8cd75b79ba2ba7d2a97585380/qiskit_ibmq_provider-0.20.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "ed27f122ae1061eb2f06961181eaa5222fb91b53a4bc511354cdecdb71a9ce04",
"md5": "a7da909a0cdfdf0868ea780a26378a65",
"sha256": "f343025ca1ddaa6aad071e53f5b4c60df798aff0f3681266a8de35e933e61a9c"
},
"downloads": -1,
"filename": "qiskit-ibmq-provider-0.20.2.tar.gz",
"has_sig": false,
"md5_digest": "a7da909a0cdfdf0868ea780a26378a65",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.7",
"size": 245217,
"upload_time": "2023-03-07T19:03:13",
"upload_time_iso_8601": "2023-03-07T19:03:13.886650Z",
"url": "https://files.pythonhosted.org/packages/ed/27/f122ae1061eb2f06961181eaa5222fb91b53a4bc511354cdecdb71a9ce04/qiskit-ibmq-provider-0.20.2.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-03-07 19:03:13",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "Qiskit",
"github_project": "qiskit-ibmq-provider",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"tox": true,
"lcname": "qiskit-ibmq-provider"
}