Ehdtd - cryptoCurrency Exchange history data to database
This class retrieves historical data from exchanges and stores it in a database.
Example:
Install
```bash
pip install ehdtd
```
Use
```python
import time
from ehdtd import Ehdtd
exchange = 'binance'
symbol = 'BTC/USDT'
interval = '1m'
limit = 10
db_data = {
'db_type': 'postgresql', # postgresql, mysql
'db_name': 'ehdtd',
'db_user': 'ehdtd',
'db_pass': 'xxxxxxxxx',
'db_host': '127.0.0.1',
'db_port': '5432'
}
fetch_data = [
{
'symbol': symbol,
'interval': interval
}
]
ehd = Ehdtd(exchange, fetch_data, db_data) # Create an instance
ehd.start() # Start fetching data
time.sleep(900) # First time Wait for available data, for the data to be updated,
# you must wait between 90 minutes and 2.5 hours depending on the interval
for v in fetch_data:
symbol = v['symbol']
interval = v['interval']
start_from = 0
until_to = None
return_type = 'pandas'
data_db = ehd.get_data_from_db(symbol, interval, start_from, until_to, return_type)
print(data_db)
print('=========================================================================')
print('')
time.sleep(1)
ehd.stop() # Stop fetching data
```
How It Works:
For Binance:
- Try to retrieve data from a file. Check this link:
Binance Public Data - If the file is not available, try to retrieve data from the API.
- Then get data from the WebSocket API using the Ccxw class.
Database Columns:
-
open_time,open_date,open_price,close_time,close_date,close_price,low,high,volume,exchange,symbol,interval,status,data -
Column
datais not used,
and columnstatuscan have three values:'__NON_CHECK__','__OK__','__ERROR__'.- If
status == '__OK__', the file has consistent data. - If
status == '__ERROR__', the file has inconsistent data. - If
status == '__NON_CHECK__', the file is not analyzed.
- If
Retrieving Data from Database:
Use the function ehd.get_data_from_db(symbol, interval, start_from, until_to, return_type):
- If
return_type == 'pandas', it returns a Pandas DataFrame. - If
return_type == 'list', it returns a list of dictionaries.
Metadata
Release files for ehdtd 0.2.44
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 |
|---|---|---|---|---|
| ehdtd-0.2.44.tar.gz | 43.0 kB | Without provenance | Details for ehdtd-0.2.44.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ehdtd-0.2.44-py3-none-any.whl | Python 3 | none | any | Details for ehdtd-0.2.44-py3-none-any.whl |
Total release size: 96.2 kB
Release files / ehdtd-0.2.44.tar.gz
| Download URL | ehdtd-0.2.44.tar.gz |
|---|---|
| Size | 43.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73ef046933ed4893554662e7923e31c1ac77524fc157facd8fa32f51e44f7cdd
|
|
BLAKE2b-256 checksum How to use checksums |
b2032cac2c114c386161cd7194d3b7b68d90dc8ad9be0df679e7d61bd3191652
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Release files / ehdtd-0.2.44-py3-none-any.whl
| Download URL | ehdtd-0.2.44-py3-none-any.whl |
|---|---|
| Size | 53.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f6e19db313c98685ccd4e5cbfe1f81d08edddd5137dd3a5598a81937c651d53
|
|
BLAKE2b-256 checksum How to use checksums |
9ef391467b1e3cc4d32858af2f440f3790683130a29e06683a8ce61049c85de6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Security for ehdtd 0.2.44
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.