CLN: remove _maybe_update_attributes
It is only non-trivial for DTI and TDI, and only actually needed in `__array_wrap__`.  It is cleaner to implement the relevant patch in `DatetimeIndexOpsMixin.__array_wrap__` and avoid the need for maybe_update_attributes altogether.


can you rebase Took a glance at the ASV portal this might have caused a lot of performance regressions:

https://pandas.pydata.org/speed/pandas/#/regressions

@jbrockmendel do you have a quick way of validating that? > do you have a quick way of validating that?

Not a quick way, no.  I'll take a look, but likely won't get to it today. Oh yea no rush - thanks! @WillAyd looking at this it isn't obvious which regressions you think may have been caused here.  I see a bunch from August 15 linking to 15b11c83; are those the ones you have in mind? Might have misread but thought that was the commit that preceded this one on master

Sent from my iPhone

> On Oct 18, 2019, at 7:06 PM, jbrockmendel <notifications@github.com> wrote:
> 
> ﻿
> @WillAyd looking at this it isn't obvious which regressions you think may have been caused here. I see a bunch from August 15 linking to 15b11c8; are those the ones you have in mind?
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or unsubscribe.
 It's indeed this commit that asv reports for the biggest regressions. But there was also a gap in asv runs between August 2 and this commit (August 15), so probably it can be anything in that window @TomAugspurger it also seems that the last runs were in September?  Will check today. We had some issues with a bad ASV env failing builds. 

> On Oct 19, 2019, at 07:05, Joris Van den Bossche <notifications@github.com> wrote:
> 
> ﻿
> @TomAugspurger it also seems that the last runs were in September?
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or unsubscribe.
