Metadata
1 maintainer
Release files for backports.pdb 2.2.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 | |
|---|---|---|---|---|
| backports.pdb-2.2.0.tar.gz | 26.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| backports.pdb-2.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 48.3 kB
Release files / backports.pdb-2.2.0.tar.gz
| Download URL | backports.pdb-2.2.0.tar.gz |
|---|---|
| Size | 26.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0232884d4ab746ffa0ce52accec2961cb8843e7ad77b4dc0f748eb22bcc81671
|
|
BLAKE2b-256 checksum How to use checksums |
d5b232054fb8a5b4758003440faab36a8cf3a6da27bf4105790a340926f62df9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / backports.pdb-2.2.0-py3-none-any.whl
| Download URL | backports.pdb-2.2.0-py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bde6082205ce55d165ee75cf41cacb593a1313a02b02726716b334da96486839
|
|
BLAKE2b-256 checksum How to use checksums |
89ae0e537113486a76fdd861a62135e07ffe5c700eed2c5d7eea2537da614487
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for backports.pdb 2.2.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.
