This release is a pre-release and may not be stable for production use.
# pystonkslib
Stonks are cool - and if you want to do your own analysis, you have to pull all the data.
## Installation
`bash pip install pystonkslib `
## CI/CD
This CI/CD assumes that there are two variables set for the upload of your pypy packages:
TWINE_PASSWORD TWINE_USERNAME
For the initial CI/CD, this is set to upload to testpypy rather than the actual pypy server. If tags are used, it will push to production pypy. This should let you differentiate between testing your package upload and actually publishing it to the pypy index.
1 maintainer
Metadata
1 maintainer
Release files for pystonkslib 0.0.4a2
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 | Actions |
|---|---|---|---|---|
| pystonkslib-0.0.4a2.tar.gz | 7.0 kB | Without provenance | Details for pystonkslib-0.0.4a2.tar.gz |
Release files / pystonkslib-0.0.4a2.tar.gz
| Download URL | pystonkslib-0.0.4a2.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd9f61c181e0a872b5c3a4bc000cab6e8ed7a1a87552b6ef68de10227d811217
|
|
BLAKE2b-256 checksum How to use checksums |
44bc2eb464e4264b65c163e5afb9bb89ad9507cb733c8bcba6c7d9936b81f4f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.55.0 CPython/3.9.1
|
Security for pystonkslib 0.0.4a2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
