We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Followings should be changed to coerce to object dtype.
object
__getitem__
.loc
GroupBy.first
DataFrame.combine_first
Index
DatetimeIndex.union
TypeError
Series.append
AttributeError
concat
IndexError
replace
The text was updated successfully, but these errors were encountered:
Since there's only one issue left, closing in favor of that issue (revived with) #21671
Sorry, something went wrong.
No branches or pull requests
Followings should be changed to coerce to
object
dtype.Coerce to tz-naive / UTC
__getitem__
) resets tz BUG/API: Make consistent API for tz-aware and tz-naive ops #11351.loc
assignment coerces to naive BUG: .loc assignment of datetime with tz is coercing to naive #11365GroupBy.first
coerces to naive Taking first row from each group in groupby sometimes strips tzinfo #10668DataFrame.combine_first
DataFrame combine_first() loses timezone information for datetime columns #10567Index
creation API: DatetimeIndex creation with mixed tz timestamps #11488 -> changed to be Index(dtype=object) (BUG/API: Index creation with different tz coerces DatetimeIndex #11696)Raises TypeError / ValueError
DatetimeIndex.union
raisesTypeError
BUG/API: Make consistent API for tz-aware and tz-naive ops #11351Bug
Series.append
raisesAttributeError
BUG: Series.append with DatetimeBlock and DatetimeTZBlock raises AttributeError #11455concat
raisesIndexError
Inconsistent concat behavior between datetime64[ns] and tz-aware version in 0.17.1 #11693replace
bug in Series.replace with timezone-aware datetime columns #11792The text was updated successfully, but these errors were encountered: