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
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
NA
Issue Description
DatetimeLikeArrayMixin.isin casts pretty aggressively. In particular I think we shouldn't be parsing strings here. We should deprecate and tell users to cast explicitly.
Expected Behavior
NA
Installed Versions
Replace this line with the output of pd.show_versions()
The text was updated successfully, but these errors were encountered:
So just to be clear, it's allowed to do e.g. dt_arr.isin(['2018-01-01', '2018-01-02']) and we should deprecate this and make the users convert to first, e.g. dt_arr.isin(pd.array(['2018-01-01', '2018-01-02'], dtype=" datetime64[ns]"))?
Pandas version checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
NA
Issue Description
DatetimeLikeArrayMixin.isin casts pretty aggressively. In particular I think we shouldn't be parsing strings here. We should deprecate and tell users to cast explicitly.
Expected Behavior
NA
Installed Versions
Replace this line with the output of pd.show_versions()
The text was updated successfully, but these errors were encountered: