-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Bug in merging datetime64[ns, tz] dtypes #11405 #11410
New issue
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
Conversation
# dtypes = set() | ||
upcast_classes = set() | ||
null_upcast_classes = set() | ||
upcast_classes = defaultdict(lambda: []) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
defaultdict(list)
avoids the need for a lambda.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep
Bug in merging datetime64[ns, tz] dtypes #11405
@jreback Is this still an issue merging on multiple tz-aware columns? pandas version:
A dtypes:
B:
B dtypes:
|
that need a nicer error message, but why would you think that should work at all? you cannot compare a tz-aware type with a tz-naive type |
yup, just realized that one was tz-aware and the other not. Sorry for that.
…On Fri, Mar 24, 2017 at 10:21 AM, Jeff Reback ***@***.***> wrote:
that need a nicer error message, but why would you think that should work
at all? you cannot compare a tz-aware type with a tz-naive type
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11410 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFQjo1aa3nm9Qi1y73KK1nWiSWXS9d8aks5ro_umgaJpZM4GTtlE>
.
--
David
|
closes #11405