-
-
Notifications
You must be signed in to change notification settings - Fork 18.3k
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
DEPR: Deprecate tupleize_cols in Index constructor #17899
Conversation
"will be removed in a future version", | ||
FutureWarning, stacklevel=2) | ||
else: | ||
tupleize_cols = True |
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.
why are you changing this?
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.
Because you said that we should deprecate this parameter back in #17060. If that's no longer the case, I can just close this.
Codecov Report
@@ Coverage Diff @@
## master #17899 +/- ##
==========================================
- Coverage 91.23% 91.22% -0.02%
==========================================
Files 163 163
Lines 50105 50111 +6
==========================================
- Hits 45715 45712 -3
- Misses 4390 4399 +9
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #17899 +/- ##
==========================================
- Coverage 91.23% 91.22% -0.02%
==========================================
Files 163 163
Lines 50105 50111 +6
==========================================
- Hits 45715 45712 -3
- Misses 4390 4399 +9
Continue to review full report at Codecov.
|
I don't think we can deprecate this. When we implement the " |
This is also what Tom mentioned in #17060 (comment)
The main thing that would not be possible with |
Ah, right...thanks for reminding me about that. I guess the deprecation does seem premature in light of the ongoing discussion in #17246. I'll close the PR but can always revisit once it gets resolved. |
I think we agree on the idea, it just needs somebody doing the work. |
Title is self-explanatory.
xref #17060.