-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
API/BUG: Index creation with named Index resets name #11193
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
Same for
|
I tried to reproduce the bug and failed. Here is a link the code examples I ran on my laptop. http://nbviewer.ipython.org/gist/mbirdi/7586ebc290bd90a73ed3 So in my examples I was able to reset the name of the index from 'x' to None. |
@mbirdi this reproduces on master
you need another index creation (e.g. with just a |
well if I have something that could be a list or an Index then I want to be able to wrap it and preserve meta data. The bottom line is that we want to have API consistency. |
I can work on this. I'll send a PR shortly. |
@jreback What should be the desired behaviour when the user passes
|
Well, one option is to use a sentinel object for the default instead, e.g., |
The last question ( |
…ame, when a new name is not provided, #11193 fix missing lines in whatsnew cosmetic change in whatsnew refactor unit test, failing for MultiIndex short sentence in whatsnew doc fix unit test remove commented code fix typo add doc string add unit test for multiindex case
closed by #11695 |
A point is whether to reset existing Index name in below case. Current impl can't distinguish whether name is not passed, or passed
None
explicitly.The text was updated successfully, but these errors were encountered: