-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
'date_range' no longer has a true "24H" frequency #8774
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
Comments
See #7825 for a similar discussion. There is a comment mentioning that 24H and D are equivalent in the context of date_range. To me 24H should be what you describe and D should retain its current behavior (did they used to be different?). |
Thx for the link, this is indeed the same issue, hope others will agree with us that "D" should be != "24H". They always have had the same semantic, but in previous pandas versions "D" and "24H" meant true 24 hours intervals: one just had to accept that "D" was exactly 24 hours to make sense of date_range behavior. Now with pandas 0.15.0, "D" and "24H" stand for "calendar daily" frequencies and it is harder to think of "24H" as a "calendar day" which can have 23, 24 or 25 hours. |
consolidated to #20633 |
The semantic of the frequencies "D" and "24H" in 'date_range' has changed in pandas 0.15.0: they are now both equivalent to a "calendar daily" frequency, ie local time is kept the same across DST transition:
But what if we do want a true "24H" frequency ? I think "D" and "24H" should not share the same semantic, Out[2] is OK but Out[3] should be:
The text was updated successfully, but these errors were encountered: