smoke-zephyr
Python utility collection
Version 2.0 – From version 2.0 onwards, Python 2.7 is no longer supported. For Python 2.7 support, use the latest 1.x version (v1.4.1).
License
smoke-zephyr is released under the BSD 3-clause license, for more details see the LICENSE file.
Supported Versions
The following version of Python are currently supported:
Python 3.4
Python 3.5
Python 3.6
Python 3.7
Code Documentation
smoke-zephyr uses Sphinx for internal code documentation. This documentation can be generated from source with the command sphinx-build docs/source docs/html. The latest documentation is kindly hosted on ReadTheDocs at smoke-zephyr.readthedocs.io.
1 maintainer
Metadata
1 maintainer
Release files for smoke-zephyr 2.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 |
|---|---|---|---|---|
| smoke-zephyr-2.0.1.tar.gz | 18.9 kB | Without provenance | Details for smoke-zephyr-2.0.1.tar.gz |
Release files / smoke-zephyr-2.0.1.tar.gz
| Download URL | smoke-zephyr-2.0.1.tar.gz |
|---|---|
| Size | 18.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0906e78d60bdce30bfbbfa4f8226e8652fec73459c1310ff46ff4fda23469e9
|
|
BLAKE2b-256 checksum How to use checksums |
16efbdd186de1196fe6dc1c7ceacdbe2745a59b4121088e4ce69cab507fa87dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.8.6
|
Security for smoke-zephyr 2.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.
