The author of this package has not provided a project description
Metadata
Release files for attrdictionary2 2.1.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 | |
|---|---|---|---|---|
| attrdictionary2-2.1.0.tar.gz | 9.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| attrdictionary2-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.8 kB
Release files / attrdictionary2-2.1.0.tar.gz
| Download URL | attrdictionary2-2.1.0.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5d4bf6c4beb7ee10fe89af17985794fde7eaee7670f6ca1b8883a3d31cdc590
|
|
BLAKE2b-256 checksum How to use checksums |
65dd79d59a6f68380039032694f39c3caffb6dcf6c233ad7601defa062e7248b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.8.10 Windows/10
|
Release files / attrdictionary2-2.1.0-py3-none-any.whl
| Download URL | attrdictionary2-2.1.0-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4d1f06153fc6c772202cef0ef84e01bdc9afca8b96e9d2af0c5940c710f56c1
|
|
BLAKE2b-256 checksum How to use checksums |
ff0af38353a0b0681403022e79361e23b29b34b0be7ca7a7295c8041489dff9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.8.10 Windows/10
|
Security for attrdictionary2 2.1.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.