-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: index name lost with timedelta ops #9926
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
Comments
Would like to define expected bahavior. Based on normal index, I understand first (left-side) index name should be prioritized.
But in case of datetime-likes, I feel it is natural that prioritize the name of
|
no priority see Index.append it may be a bug if add ops don't follow this pattern |
Thanks, could you check following understanding is correct for both set (intersection, etc) and arithmetic ops (addition, etc)?
Based on above understanding, normal index behaves incorrectly. All the below ops should reset the name to
|
@sinhrks Yes, I think you correctly understand this now. Here are some notes on this from @cpcloud: blaze/blaze#458 (comment) |
ref: #9862
The text was updated successfully, but these errors were encountered: