This is where you should write a short paragraph that describes what your module does, how it does it, and why people should use it.
PyPI |
pip install i10-bluesky |
Source code |
|
Releases |
This is where you should put some images or code snippets that illustrate some relevant examples. If it is a library then you might put some introductory code here:
from i10_bluesky import __version__
print(f"Hello i10_bluesky {__version__}")Or if it is a commandline tool then you might put some example commands here:
$ python -m i10_bluesky --version
1 maintainer
Metadata
1 maintainer
Release files for i10-bluesky 0.0.1
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 |
|---|---|---|---|---|
| i10-bluesky-0.0.1.tar.gz | 46.8 kB | Without provenance | Details for i10-bluesky-0.0.1.tar.gz |
Release files / i10-bluesky-0.0.1.tar.gz
| Download URL | i10-bluesky-0.0.1.tar.gz |
|---|---|
| Size | 46.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d17357294a9f35b09b0f6d345a1dec4ca13cd2ebe58ba645aa3e6f5e46e38de3
|
|
BLAKE2b-256 checksum How to use checksums |
5ee1f391a3dca57b91688c0b29a5b9385f8fb26dd6ee390611576d040ec1cabb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.5
|
Security for i10-bluesky 0.0.1
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.
