The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for AutoDiffpyy 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 | |
|---|---|---|---|---|
| AutoDiffpyy-1.0.tar.gz | 13.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| AutoDiffpyy-1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.9 kB
Release files / AutoDiffpyy-1.0.tar.gz
| Download URL | AutoDiffpyy-1.0.tar.gz |
|---|---|
| Size | 13.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b99e2d6f2fe0761fa4d6a0aa9f74ddcc4a538ba4826e4f133dd02a44a889692
|
|
BLAKE2b-256 checksum How to use checksums |
ee6a86f1dc864429f228d289f246a089ce61737704802c89c912469d1ac42b58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Release files / AutoDiffpyy-1.0-py3-none-any.whl
| Download URL | AutoDiffpyy-1.0-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa9419d1b755a531ae489c5252bb0275cf98b1a6afa4a0cb5837ccec1383ec4a
|
|
BLAKE2b-256 checksum How to use checksums |
b18747290fcc79e15a102de31d2b6a9ebf9a6d181a9149565148fd76b0804cf0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for AutoDiffpyy 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.
