Metadata
1 maintainer
Release files for quant1x-xtquant 2025.5.28
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 | |
|---|---|---|---|---|
| quant1x_xtquant-2025.5.28.tar.gz | 34.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quant1x_xtquant-2025.5.28-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.3 MB
Release files / quant1x_xtquant-2025.5.28.tar.gz
| Download URL | quant1x_xtquant-2025.5.28.tar.gz |
|---|---|
| Size | 34.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6de91f4429a1560a38c83f13d1a7695cc51e2441d89ddda0f77d04b96c73ae5b
|
|
BLAKE2b-256 checksum How to use checksums |
8a383190a362113c4dbdbc4a3b6221834df0b4fa54ec77a0091dda5b03db2232
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / quant1x_xtquant-2025.5.28-py3-none-any.whl
| Download URL | quant1x_xtquant-2025.5.28-py3-none-any.whl |
|---|---|
| Size | 34.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc5c4acb0170832b7d3fbd04ccd9afeb139081e7a33972d363df4647f6398aab
|
|
BLAKE2b-256 checksum How to use checksums |
345ec5c541c178da0169e086edc651cf5e6cbfdc74bdaa25d6e99cb10b3754c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for quant1x-xtquant 2025.5.28
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.
