The author of this package has not provided a project description
4 maintainers
Metadata
4 maintainers
Release files for nameko-tracer 1.4.0
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 | |
|---|---|---|---|---|
| nameko-tracer-1.4.0.tar.gz | 10.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nameko_tracer-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.7 kB
Release files / nameko-tracer-1.4.0.tar.gz
| Download URL | nameko-tracer-1.4.0.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ceb7a7dfcc3ad3406ed73ef80558094ba24d9afaf9d2b8c63ae3f0a4ddce7f67
|
|
BLAKE2b-256 checksum How to use checksums |
c6d7319cc5a38780b0f0f25cb00dd1a0f0e6c29417962f57a1b4c0be770b9550
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.1
|
Release files / nameko_tracer-1.4.0-py3-none-any.whl
| Download URL | nameko_tracer-1.4.0-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11efafe5bcc9d09cef2efdcd81fb6dd04ac840dea9a59724190e4c5085cdbad6
|
|
BLAKE2b-256 checksum How to use checksums |
873521ffea90d58cdc21fdff27340d24e06d5f135b9f89b241ad6ce9dc738f49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.1
|
Security for nameko-tracer 1.4.0
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.
