-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
API: 'D' and offset.Day always represents calendar day #22867
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
Conversation
This reverts commit 16de58d.
Hello @mroeschke! Thanks for updating the PR.
Comment last updated on December 13, 2018 at 23:43 Hours UTC |
doc/source/whatsnew/v0.24.0.txt
Outdated
See the :ref:`documentation here <timeseries.dayvscalendarday>` for more information. | ||
:class:`Day` and associated frequency alias ``'D'`` will always respect | ||
calendar day arithmetic | ||
(:issue:`22864`, :issue:`20596`, :issue:`16980`, :issue:`8774`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
u can add this PR number as well
@mroeschke I will try to give this a look (finally, sorry about that). Can you give a short status update? Are there still problems you are encountering, .. ? |
One of the example I used in the discussion is now errorring:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do you see the way forward here with _Day
. Is the idea that Day
will be replaced by that, after deprecating the behaviours that are different?
(but I don't see any deprecations right now?)
@@ -1136,6 +1096,7 @@ Deprecations | |||
- :func:`pandas.types.is_datetimetz` is deprecated in favor of `pandas.types.is_datetime64tz` (:issue:`23917`) | |||
- Creating a :class:`TimedeltaIndex` or :class:`DatetimeIndex` by passing range arguments `start`, `end`, and `periods` is deprecated in favor of :func:`timedelta_range` and :func:`date_range` (:issue:`23919`) | |||
- Passing a string alias like ``'datetime64[ns, UTC]'`` as the `unit` parameter to :class:`DatetimeTZDtype` is deprecated. Use :class:`DatetimeTZDtype.construct_from_string` instead (:issue:`23990`). | |||
- Operations where the offset alias ``'D'`` or :class:`Day` acts as a fixed, absolute duration of 24 hours are deprecated. This includes :class:`Timestamp` arithmetic and all operations with :class:`Timedelta`. :class:`Day` will always represent a calendar day in a future version (:issue:`22864`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you give some examples here?
For example, with the following I don't see a change or warning:
In [11]: pd.Timestamp("2012-10-28", tz='Europe/Brussels') + pd.offsets.Day()
Out[11]: Timestamp('2012-10-28 23:00:00+0100', tz='Europe/Brussels')
Sorry, I have been primarily working on reverting things and getting the test to pass again by rolling back TODO
Migration Concern Example: |
Closing in favor of #24330 for now (reverts behavior to pre- |
git diff upstream/master -u -- "*.py" | flake8 --diff