You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
commit 23e5cfc
Author: Tom Augspurger <[email protected]>
Date: Tue Oct 2 13:10:41 2018 -0500
Use ._tshift internally for datetimelike ops
In preperation for PeriodArray / DatetimeArray / TimedeltaArray.
Index.shift has a different meaning from ExtensionArray.shift.
- Index.shift pointwise shifts each element by some amount
- ExtensionArray.shift shits the *position* of each value in the array
padding the end with NA
This is going to get confusing. This PR tries to avoid some of that by
internally using a new `_tshift` method (time-shift) when we want to do pointwise
shifting of each value. Places that know they want that behavior (like in the
datetimelike ops) should use that.
commit 1d9f76c
Author: Joris Van den Bossche <[email protected]>
Date: Tue Oct 2 17:11:11 2018 +0200
CLN: remove Index._to_embed (pandas-dev#22879)
* CLN: remove Index._to_embed
* pep8
commit 6247da0
Author: Tom Augspurger <[email protected]>
Date: Tue Oct 2 08:50:41 2018 -0500
Provide default implementation for `data_repated` (pandas-dev#22935)
commit 5ce06b5
Author: Matthew Roeschke <[email protected]>
Date: Mon Oct 1 14:22:20 2018 -0700
BUG: to_datetime preserves name of Index argument in the result (pandas-dev#22918)
* BUG: to_datetime preserves name of Index argument in the result
* correct test
Copy file name to clipboardExpand all lines: doc/source/whatsnew/v0.24.0.txt
+1
Original file line number
Diff line number
Diff line change
@@ -655,6 +655,7 @@ Datetimelike
655
655
- Bug in :class:`DatetimeIndex` incorrectly allowing indexing with ``Timedelta`` object (:issue:`20464`)
656
656
- Bug in :class:`DatetimeIndex` where frequency was being set if original frequency was ``None`` (:issue:`22150`)
657
657
- Bug in rounding methods of :class:`DatetimeIndex` (:meth:`~DatetimeIndex.round`, :meth:`~DatetimeIndex.ceil`, :meth:`~DatetimeIndex.floor`) and :class:`Timestamp` (:meth:`~Timestamp.round`, :meth:`~Timestamp.ceil`, :meth:`~Timestamp.floor`) could give rise to loss of precision (:issue:`22591`)
658
+
- Bug in :func:`to_datetime` with an :class:`Index` argument that would drop the ``name`` from the result (:issue:`21697`)
0 commit comments