-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
MultiIndex copies don't have _id field set. #9967
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
If we add |
Found why 1052 if not _all_indexes_same(indexes):
#functionality to actually concat multiindex
...
...
1095 new_index = indexes[0] So, if we think that all indexes are the same we just take the first one. def _all_indexes_same(indexes):
first = indexes[0]
for index in indexes[1:]:
if not first.equals(index):
return False
return True It calls function I'll rename the Issue. |
I don't recall why this was done like this. You can try changing and see what pops up in the test suite. |
Tests seem to be unharmed:
|
Add additional test + fix int32 error
…ndas-dev#14936) Add additional test + fix int32 error
I have stumbled across a curious issue when working with
pandas.concat
.Let's consider a simple example:
The output is as expected:
Strange thing will happen if we pass to
concat
not an original dict but a deepcopy of it:The output, surprisingly, will be:
Thus meaning, that the multiindex of the first DataFrame was taken two times.
Contents of the copied dict though seems to be correct at first glance:
PS. Version information:
Issue is reproducible down to version 0.15.0. Version 0.14.1 is fine.
The text was updated successfully, but these errors were encountered: