Welcome to Bloqade Circuit -- A component package of QuEra's Neutral Atom SDK
Bloqade is a Python SDK for neutral atom quantum computing. It provides a set of embedded domain-specific languages (eDSLs) for programming neutral atom quantum computers. Bloqade is designed to be a high-level, user-friendly SDK that abstracts away the complexities of neutral atom quantum computing, allowing users to focus on developing quantum algorithms and compilation strategies for neutral atom quantum computers.
Bloqade-circuit provides the core components of representing quantum circuits for bloqade.
Installation
Install via uv (Recommended)
uv add bloqade-circuit
Documentation
The documentation is available at https://bloqade.quera.com/latest/. We are at an early stage of completing the documentation with more details and examples, so comments and contributions are most welcome!
Contributing
We welcome contributions! Please check the contribution guidelines for a detailed guide.
License
Apache License 2.0 with LLVM Exceptions
Metadata
Release files for bloqade-circuit 0.15.3
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 | |
|---|---|---|---|---|
| bloqade_circuit-0.15.3.tar.gz | 521.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bloqade_circuit-0.15.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 843.1 kB
Release files / bloqade_circuit-0.15.3.tar.gz
| Download URL | bloqade_circuit-0.15.3.tar.gz |
|---|---|
| Size | 521.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1f6535086e5ddabccefbe018a4372bfa34668a29c103ef4b82ff15b7ef9fe58
|
|
BLAKE2b-256 checksum How to use checksums |
751630dcb54074ce615e6274762b0438424bf29b82673740b0514b0a19ea0742
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency logRelease files / bloqade_circuit-0.15.3-py3-none-any.whl
| Download URL | bloqade_circuit-0.15.3-py3-none-any.whl |
|---|---|
| Size | 321.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60aed392f09e6149fbfcefa7b43a9f12863f0d9205e58e91eb2d1571d4cde4d6
|
|
BLAKE2b-256 checksum How to use checksums |
38a5e5db6eefae2cafeade34ac1daf9622a4cb6a8d12bde96993022338dc9510
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency logSecurity for bloqade-circuit 0.15.3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for bloqade_circuit-0.15.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency logA 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.