1 maintainer
Metadata
1 maintainer
Release files for gridsource 2.3.2
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 | |
|---|---|---|---|---|
| gridsource-2.3.2.tar.gz | 24.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gridsource-2.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 50.5 kB
Release files / gridsource-2.3.2.tar.gz
| Download URL | gridsource-2.3.2.tar.gz |
|---|---|
| Size | 24.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f49c1da00a4bf70c657916a49526d9013928f9af88efefc046eb7a593ff722a3
|
|
BLAKE2b-256 checksum How to use checksums |
c50368ec135657a58d1987c9b3c87358a409390decb0533528cb589251fd2388
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.11.8 Linux/6.8.0-79-generic
|
Release files / gridsource-2.3.2-py3-none-any.whl
| Download URL | gridsource-2.3.2-py3-none-any.whl |
|---|---|
| Size | 26.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4319c395d440853aae7dbabac8f09a1fd854fde8cbd674f56de94ade145e0919
|
|
BLAKE2b-256 checksum How to use checksums |
b40c27bb4242e632c7eea847fc0aef4b1c54e24cf8bcded8f18b9cb4dbf3a80a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.11.8 Linux/6.8.0-79-generic
|
Security for gridsource 2.3.2
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.
