# trader
#### 介绍 python实现的自动化交易员
Metadata
Release files for quant1x-trader 0.8.18
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_trader-0.8.18.tar.gz | 27.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quant1x_trader-0.8.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.2 kB
Release files / quant1x_trader-0.8.18.tar.gz
| Download URL | quant1x_trader-0.8.18.tar.gz |
|---|---|
| Size | 27.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9459e08bac8e021d36b0694479caf1e6859cfc957631ec892de05f6f9c96abbc
|
|
BLAKE2b-256 checksum How to use checksums |
ebd27f2eeba005e826b98fb89afd4469f1a38f95b4d0c5c6f84ce14ed27475ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / quant1x_trader-0.8.18-py3-none-any.whl
| Download URL | quant1x_trader-0.8.18-py3-none-any.whl |
|---|---|
| Size | 30.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2c08fed8ba991476b747e77b5131c450440713dd4b43fd90e64ce8cdc176658
|
|
BLAKE2b-256 checksum How to use checksums |
3c186deca9edd09d9b81257dbdff787a1196e845650507160a175d27205a97b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for quant1x-trader 0.8.18
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.