Open algonitish opened 5 years ago
I'm having a similar issue. While trying to ingest non-USA data, the bundle registration simply fails for not having the same timezone. Leaving as UTC leads to successful ingestion, but I assume if I had intraday data, the timestamps would be wrong. Here my error message when setting a non UTC timezone:
File "zipline/data/bundles/core.py", line 400, in ingest
end_session,
File "zipline/data/us_equity_pricing.py", line 201, in __init__
"Start session %s is invalid!" % start_session
ValueError: Start session 2017-01-03 00:00:00-02:00 is invalid!
I have the same problem! zipline works only with utc timezone.
Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment
Now that you know a little about me, let me tell you about the issue I am having:
Description of Issue
register_calendar()
Here is how you can reproduce this issue on your machine:
Reproduction Steps
What steps have you taken to resolve this already?
The error traces to line 75 of trading_calendar.py with the function:
_all_days = date_range(start, end, freq=self.day, tz='UTC')
here tz='UTC' is hardcoded, which makes it impossible for any other timezone to be verified. I would have rewritten this part, but the fact that it exists means that there's a workaround or something I am not doing correctly.Anything else?
As opposed to following the
csvdir
method I have rolled my own procedure for creating a panel from market data I am getting from my brokers. The end result I am aiming for is running the most basic zipline.run_algorithm() with a trading_calendar=[the above NSE calendar]Sincerely, algonitish