This project has been archived by its maintainers, and is no longer receiving any updates.
Q# Interoperability for Python
The qsharp package for Python provides interoperability with the Quantum Development Kit and with the Q# language, making it easy to simulate Q# operations and functions from within Python.
For details on how to get started with Python and Q#, please see the Getting Started with Python guide.
You can also try our Quantum Computing Fundamentals learning path to get familiar with the basic concepts of quantum computing, build quantum programs, and identify the kind of problems that can be solved.
Installing with Anaconda
If you use Anaconda or Miniconda, installing the qsharp package will automatically include all dependencies:
conda install -c quantum-engineering qsharp
Installing from Source
If you'd like to contribute to or experiment with the Python interoperability feature, it may be useful to install from source rather than from the qsharp package on the Python Package Index (PyPI).
To do so, make sure that you are in the Python/qsharp directory, and run setup.py with the install argument:
cd Python/qsharp
python setup.py install
Building the qsharp Package
The Python interoperability feature uses a standard setuptools-based packaging strategy.
To build a platform-independent wheel, run the setup script with bdist_wheel instead:
cd Python/qsharp
python setup.py bdist_wheel
By default, this will create a qsharp wheel in dist/ with the version number set to 0.0.0.1.
To provide a more useful version number, set the PYTHON_VERSION environment variable before running setup.py.
Support and Q&A
If you have questions about the Quantum Development Kit and the Q# language, or if you encounter issues while using any of the components of the kit, you can reach out to the quantum team and the community of users in Stack Overflow and in Quantum Computing Stack Exchange tagging your questions with q#.
1 maintainer
Metadata
1 maintainer
Release files for qsharp 0.28.277227
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qsharp-0.28.277227.tar.gz | 2.7 kB | Without provenance | Details for qsharp-0.28.277227.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qsharp-0.28.277227-py3-none-any.whl | Python 3 | none | any | Details for qsharp-0.28.277227-py3-none-any.whl |
Total release size: 4.9 kB
Release files / qsharp-0.28.277227.tar.gz
| Download URL | qsharp-0.28.277227.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5637f369161fd2399a8428763fdfd700800206b01a9cad4241e78eb7564da47c
|
|
BLAKE2b-256 checksum How to use checksums |
9f9284153ae73b11bdf8c1bc3912bed122ebf00f268d1cc90b63fa484341c22f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Release files / qsharp-0.28.277227-py3-none-any.whl
| Download URL | qsharp-0.28.277227-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
747b368f143ca420fa28c963d626982bcc9fb08613998fba2819144ac5612e32
|
|
BLAKE2b-256 checksum How to use checksums |
073c52c2f6ffd08891edf6fea49fe87b188e7cb197f8ebe217f6474b5573dc2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Security for qsharp 0.28.277227
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
