The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pydataxm 0.3.19
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 | |
|---|---|---|---|---|
| pydataxm-0.3.19.tar.gz | 20.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pydataxm-0.3.19-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 37.3 kB
Release files / pydataxm-0.3.19.tar.gz
| Download URL | pydataxm-0.3.19.tar.gz |
|---|---|
| Size | 20.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
83b6738b469c5766b7cb077a11f9f3d4e0903ff86650b78538c2bc25d009c8c6
|
|
BLAKE2b-256 checksum How to use checksums |
23f1a27786e1a324a2805b27780cabbb1234faca8466e4944bd74e2ec56376f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / pydataxm-0.3.19-py3-none-any.whl
| Download URL | pydataxm-0.3.19-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
452f45d6a579147fbba2cd23df8feb3084927d266fa66651a2959e26c2a49c69
|
|
BLAKE2b-256 checksum How to use checksums |
20240f0f7a646222996c9f84062423a0cc7a096c59ba5fac594deeb379ad83c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for pydataxm 0.3.19
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.
