# aiocrypto_prices
Very early version - API WILL CHANGE!
If you happen to stumble upon this library, please provide any and all feedback through any means comfortable to you.
## Install
$ pipenv install aiocrypto_prices
or
$ pip install aiocrypto_prices –user
## Usage
Behind the scenes we are (currently) using cryptocompare’s API, which means all of the symbols need to be in their format and supported by them.
### Simple
`python >> from aiocrypto_prices import currencies >> await currencies.ETH.prices.get('USD') 1053.28 `
### Advanced
Useful for loading things in parallel.
Careful, if you’re not accessing the target price through get, it might not reload after cache expires `python >> from aiocrypto_prices import currencies >> currencies.add('BTC', 'ETH', 'IOT') >> await currencies.load_all() >> currencies.IOT.prices.USD 2.79 `
### Setting up extra options
`python >>> from aiocrypto_prices import currencies >>> currencies.cache = 120 # 2 minute cache >>> currencies.target_currencies.append('EUR') # In addition to defaults, let's fetch EUR too. >>> currencies.extra_information = True # Get name and url of a logo `
or
`python >>> from aiocrypto_prices import Currencies >>> currencies = Currencies(cache=120, target_currencies=['USD', 'EUR'], extra_information=True) `
## Changelog
### 0.0.3
extra_information parameter was renamed to human
- new paramter ‘full’ providing market cap and supply
More data should be provided with ‘full’, but requires a redesign of Prices class
## TODO
all the TODOs scattered around the code
All the available information cryptocompare offers
- Assign amount in that currency? - perhaps aiocrypto_folio?
Implement adding together currencies of the same symbol and possibly other interactions
aiocrypto_exchanges
aiocrypto_pools
Metadata
Release files for aiocrypto-prices 0.0.3
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 |
|---|---|---|---|---|
| aiocrypto_prices-0.0.3.tar.gz | 5.4 kB | Without provenance | Details for aiocrypto_prices-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aiocrypto_prices-0.0.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for aiocrypto_prices-0.0.3-py2.py3-none-any.whl |
Total release size: 13.5 kB
Release files / aiocrypto_prices-0.0.3.tar.gz
| Download URL | aiocrypto_prices-0.0.3.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31a9eb3c038203e6f84e5d31e8ef7144c7322558c310fa3894dcc13fffd1d08d
|
|
BLAKE2b-256 checksum How to use checksums |
d1e022eeeefd8e29fcd5bb799d24df8fa60648b0545705a82f9d4e9260150187
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / aiocrypto_prices-0.0.3-py2.py3-none-any.whl
| Download URL | aiocrypto_prices-0.0.3-py2.py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
e445d80cf98432add3721b772bafbcaf2c23ecfd44721d4a805765280688776f
|
|
BLAKE2b-256 checksum How to use checksums |
8e9905bb3158e64406bae4e1132e176b108f029f7b07f1daefaaaec4de26a5b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for aiocrypto-prices 0.0.3
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.