I encountered recently issue with getting historical data during runtime app, for example Pyqt5 or even
running it on jupyter notebook. Here is example data:
Time now: 2023-06-13 12:07:23.156518
Time of data: 2023-06-13 02:09:00
{'time': 1686614940,
'high': 25901.76,
'low': 25894.92,
'open': 25895.07,
'volumefrom': 4.707,
'volumeto': 121916.59,
'close': 25901.42,
'conversionType': 'direct',
'conversionSymbol': ''}
The reason of that difference of time is because i ran kernel at night.
It always returns the data from the time kernel was started, so to get the real time data i would have to restart the kernel.
The same thing happens when using application in Pyqt5. However using cryptocompare.get_price(...) it always returns the newest value. Somewhere i read that it could be caching mechanism implemented in the library I am not sure if it was meant to be like this. Is there any solution to overcome this problem? Maybe it's only at my side and just can't address the issue.
I encountered recently issue with getting historical data during runtime app, for example Pyqt5 or even
running it on jupyter notebook. Here is example data:
Time now: 2023-06-13 12:07:23.156518
Time of data: 2023-06-13 02:09:00
The reason of that difference of time is because i ran kernel at night.
It always returns the data from the time kernel was started, so to get the real time data i would have to restart the kernel.
The same thing happens when using application in Pyqt5. However using
cryptocompare.get_price(...)it always returns the newest value. Somewhere i read that it could be caching mechanism implemented in the library I am not sure if it was meant to be like this. Is there any solution to overcome this problem? Maybe it's only at my side and just can't address the issue.