The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for deepsklearn 1.0.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 | |
|---|---|---|---|---|
| deepsklearn-1.0.0.tar.gz | 9.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deepsklearn-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.0 kB
Release files / deepsklearn-1.0.0.tar.gz
| Download URL | deepsklearn-1.0.0.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
036f0cf007a6bf623c6acc487b08a1b4c4782ed7047815fe08582b8a007e61ee
|
|
BLAKE2b-256 checksum How to use checksums |
760f7d08e308a497213e6d98de4c0db85fe434fe8e3a7c33ecfbe7695a604eb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.18
|
Release files / deepsklearn-1.0.0-py3-none-any.whl
| Download URL | deepsklearn-1.0.0-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
69470d2ecfa4a5ad5a9f6eb9996d1efbd22eb489ab106c58235c721bb8b7cb06
|
|
BLAKE2b-256 checksum How to use checksums |
d8cf63c557325c9a506b82e22e64ddd7ab53de1dc68a8c4ca7ded6b3c5580ba0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.18
|
Security for deepsklearn 1.0.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.
