ENH: add .normalize() to Timestamp?

[jorisvandenbossche]

From http://stackoverflow.com/questions/26882499/reset-time-part-of-a-pandas-timestamp#26882499

There is now a DatetimeIndex.normalize() method to set times to midnight.
Would it be useful to also have this method available on the individual Timestamp object?

Further, this method could also be added to the .dt accessor (udpate: for this, there already is a similar issue: #5502).

[jreback]

sure though I don't think is used much in the docs / maybe should have an example
(also using replace to do the same thing)

[jorisvandenbossche]

yes, indeed, Timestamp.replace(hour=0, minute=0, second=0) does the same, so maybe this is not needed.
But replace is then not available on DatetimeIndex, so it would be nice you can use the same method (one of both) on both Timestamp as DatetimeIndex/.dt accessor

[rockg]

I was thinking this the other day. Be careful because Timestamp.replace(hour=0, minute=0, second=0) does not do the right thing on DST days as it does not change the timezone offset. I was going to change normalize_date in tslib to do the right thing (see my comment in #5172).

[rockg]

DatetimeIndex.normalize() does do the right thing on these transition days so it would make sense to replicate this good behavior.

[jorisvandenbossche]

I think the fact that Timestamp.replace does not fully what is desired on DST transition days, that is an incentive to add a normalize method to Timestamp?

[rockg]

Agree, and that would be done with tslib.normalize_date (or at least the name suggests so) which is used in many places and does a straight replace.

[rockg]

Although looking further I see date_normalize (used by DatetimeIndex), normalize_date which I see used by individual Timestamps.

[jorisvandenbossche]

I would think it should not do a straight replace, as this is causing the timezone issue?