CLN: unify __finalize__ treatment for Series ops
ATM we have three slightly different usages for the arithmetic, comparison and logical ops, with no clear reason for the differences.  This changes that to make the arithmetic the one true version, which has the added benefit of letting us share _construct_result code across these three functions.

any additional tests needed? > any additional tests needed?

I'm inclined towards "no" because the behavior that is affected is stuff we don't particularly care about. Just to verify, we don't have any cases where we pass a DataFrame to `Series.__finalize__` right?

On my disallow-duplicates I noticed some strange behavior with DataFrame's having a `name` column, since we did `self.name = getattr(other, 'name', None)`, which tried to set `Series.name` to the `name` column in the DataFrame. > Just to verify, we don't have any cases where we pass a DataFrame to Series.__finalize__ right?

Not in this file, no. LGTM then.

On Tue, Sep 24, 2019 at 11:10 AM jbrockmendel <notifications@github.com>
wrote:

> Just to verify, we don't have any cases where we pass a DataFrame to
> Series.*finalize* right?
>
> Not in this file, no.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/pandas-dev/pandas/pull/28590?email_source=notifications&email_token=AAKAOIUHL3G7RCOKTJFBBX3QLI3YNA5CNFSM4IZXYXJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7O5DPQ#issuecomment-534630846>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAKAOIXHGA2V44FSS3LV66DQLI3YNANCNFSM4IZXYXJA>
> .
>
 thanks!