Hello,
First thanks for the library, I think the macro historics are a real plus to any other already existing libraries.
I seem to receive times of macro events in local machine terms as opposed to UTC which would be best in order to avoid issues with Daylight summer/winter changes (I assume GMT is same as UTC here).
For instance:
on the 26Sep investpy gives event at 19h45 => European Time
while it should say time 16h45=> GMT (3 hours less accounting for daylight)
At the moment, I am not sure how to use the data historically when compared against intradays of stock prices for instance.
I tried to use the timezone parameter without success.
Let me know your thoughts please.
I have included the bellow link to stackoveflow in case this is of any help.
Hello, First thanks for the library, I think the macro historics are a real plus to any other already existing libraries.
I seem to receive times of macro events in local machine terms as opposed to UTC which would be best in order to avoid issues with Daylight summer/winter changes (I assume GMT is same as UTC here).
For instance:
on the 26Sep investpy gives event at 19h45 => European Time
while it should say time 16h45=> GMT (3 hours less accounting for daylight)
At the moment, I am not sure how to use the data historically when compared against intradays of stock prices for instance.
I tried to use the timezone parameter without success.
Let me know your thoughts please.
I have included the bellow link to stackoveflow in case this is of any help.
https://stackoverflow.com/questions/79797/how-to-convert-local-time-string-to-utc see John Millikin answer which I thought was th emost relevant.
Best and thank you again for the lib