-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for different timezones #40
Comments
This was referenced Mar 3, 2024
This was referenced Mar 11, 2024
Closed
13 tasks
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When supplying a start_date/end_date, only UTC is supported. They are converted to the local timezone which is then fed into ddl. The timezones are consistent,
date_start="2022-01-01"
givest0=2022-01-01 01:00:00+01:00
. Consider to add support for different timezones, and use the what you give is what you get principle (timezone-wise). In that case, we also need to check if the timezones fromdate_start
anddate_end
are equal.Todo:
ddlpy.measurements_latest()
andddlpy.measurements_amount()
. This also makes sure that the behaviour does not change with respect to older ddlpy versions.ddlpy.measurements()
, also for other functions if neededWhat I Did
When adding timezones, we get
"ValueError: Not naive datetime (tzinfo is already set)"
:Validation for timezones (independent of input tz, output tz is always MET, but this is accounted for in hatyan ddl code). It also succeeds when adjusting
tz_ddl
. This is a useful testcase however:Gives:
Get the timezone from a string with
pd.Timestamp
to add todf.index
:The text was updated successfully, but these errors were encountered: