Overview
Python library for thenewboston.
Project Setup
Follow the steps below to set up the project on your environment. If you run into any problems, feel free to leave a GitHub Issue or reach out to any of our communities above.
Install required packages:
pip3 install -r requirements.txt
Testing
To run tests:
pytest
Building
To produce a source distribution:
python3 setup.py sdist
Community
Join the community to stay updated on the most recent developments, project roadmaps, and random discussions about completely unrelated topics.
License
thenewboston is MIT licensed.
Metadata
Release files for thenewboston-python-client 0.0.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 | Actions |
|---|---|---|---|---|
| thenewboston-python-client-0.0.2.tar.gz | 1.8 kB | Without provenance | Details for thenewboston-python-client-0.0.2.tar.gz |
Release files / thenewboston-python-client-0.0.2.tar.gz
| Download URL | thenewboston-python-client-0.0.2.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad3f196169fec93c6e986c60feab28fee2f3c33dfe85c9fbba74ada3c072871a
|
|
BLAKE2b-256 checksum How to use checksums |
59c2bd10871955907f4663e13ba21108545731e4433c8d996a57e192385dd006
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.24.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.7.3
|
Security for thenewboston-python-client 0.0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.