The author of this package has not provided a project description
Metadata
Release files for pypomes-db 3.2.8
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 | |
|---|---|---|---|---|
| pypomes_db-3.2.8.tar.gz | 73.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pypomes_db-3.2.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 165.6 kB
Release files / pypomes_db-3.2.8.tar.gz
| Download URL | pypomes_db-3.2.8.tar.gz |
|---|---|
| Size | 73.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c0ab0621fd74e39db76aac8af26f6e76bfadb1f9e07f87d44dd958790cbe59de
|
|
BLAKE2b-256 checksum How to use checksums |
a5b537a4474930769f0dd60be424729437a0c9875da028c4dd85ad68cdb46187
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Release files / pypomes_db-3.2.8-py3-none-any.whl
| Download URL | pypomes_db-3.2.8-py3-none-any.whl |
|---|---|
| Size | 91.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d770483c5fc3d5aedaa6bc61d1c02dce25f7672418caf21ed8be66a8bb53e80
|
|
BLAKE2b-256 checksum How to use checksums |
6302287b1e0debb6734c5d615ce9f3a402c990b0c205a0ae8ea05c5441880694
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Security for pypomes-db 3.2.8
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.