Release files for bluesky-queueserver 0.0.25
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 | |
|---|---|---|---|---|
| bluesky_queueserver-0.0.25.tar.gz | 633.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bluesky_queueserver-0.0.25-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / bluesky_queueserver-0.0.25.tar.gz
| Download URL | bluesky_queueserver-0.0.25.tar.gz |
|---|---|
| Size | 633.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d597c5c00a0b016d77991a841b916aaa880d6623318e9105b72b95a6cd0fdb1
|
|
BLAKE2b-256 checksum How to use checksums |
8a6f85931e7051bf2adb474c3742b4451d768eb4dbdb7e71f56e9ee7bbbf68d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / bluesky_queueserver-0.0.25-py3-none-any.whl
| Download URL | bluesky_queueserver-0.0.25-py3-none-any.whl |
|---|---|
| Size | 390.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
489a0304343c52942cdef52357895c1dc0c38b18931c3c9e924e5762ff0eea05
|
|
BLAKE2b-256 checksum How to use checksums |
66a354b9d35d9f2e6b4a2546212c1b0df4412a97c4323223a1f9ace8ee22689f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for bluesky-queueserver 0.0.25
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.
