GearScore python client
The package provides functionality to calculate GS for an item, with possibility to save items to local DB (sqlite).
How to use
Create table before first package usage, it can be done with:
from gear_score.db import ensure_tables_created
await ensure_tables_created()
After that, you can get info about a single item:
from gear_score.getters import PublicDbGetter
getter = PublicDbGetter()
item = await getter.get(40633)
print(item.gs)
You can get info about multiple items at once, first checking in local db and then in public:
from gear_score.utils import get_items_from_local_or_remote
items = await get_items_from_local_or_remote(50444, 50445, 50446)
TODO:
- tests
- proper documentation
- logging
- automatic db tables creation
Metadata
Release files for gear-score 0.0.4
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 | |
|---|---|---|---|---|
| gear_score-0.0.4.tar.gz | 5.7 kB | Without provenance | Details |
Release files / gear_score-0.0.4.tar.gz
| Download URL | gear_score-0.0.4.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4748a2ee05453409ef3e6a7b1b57619cf367bed4cc876d66f70ed1af3c7f1519
|
|
BLAKE2b-256 checksum How to use checksums |
abd069c668f950f1d883b7d58a0ac001388dc2312f7cbcca30e048d3cd264076
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.10
|
Security for gear-score 0.0.4
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.