-
-
Notifications
You must be signed in to change notification settings - Fork 18k
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 read_csv #17820
DEPR: Deprecate tupleize_cols in read_csv #17820
Conversation
6ba8d46
to
ee4e218
Compare
Codecov Report
@@ Coverage Diff @@
## master #17820 +/- ##
==========================================
- Coverage 91.26% 91.24% -0.02%
==========================================
Files 163 163
Lines 49980 49982 +2
==========================================
- Hits 45613 45606 -7
- Misses 4367 4376 +9
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #17820 +/- ##
==========================================
- Coverage 91.24% 91.22% -0.02%
==========================================
Files 163 163
Lines 49992 49994 +2
==========================================
- Hits 45613 45606 -7
- Misses 4379 4388 +9
Continue to review full report at Codecov.
|
ee4e218
to
75eb513
Compare
doc/source/whatsnew/v0.21.0.txt
Outdated
@@ -716,6 +716,7 @@ Deprecations | |||
|
|||
- :func:`read_excel()` has deprecated ``sheetname`` in favor of ``sheet_name`` for consistency with ``.to_excel()`` (:issue:`10559`). | |||
- :func:`read_excel()` has deprecated ``parse_cols`` in favor of ``usecols`` for consistency with :func:`read_csv` (:issue:`4988`) | |||
- :func:`read_csv()` has deprecated the ``tupleize_cols`` argument (:issue:`17060`) |
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.
you can say that this will always convert to a MI
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, done.
minor comment. merge when ready. |
@gfyoung The warning does not seem to appear when doing |
@jorisvandenbossche : That's deliberate. We only issue a warning on non-default arguments. Also, |
75eb513
to
bee9012
Compare
Why do we do that deliberately? |
You mean 'non-default' arguments? |
Oops, yes 😄
That's possible. My concern is that's going to be confusing to a user if they see That being said, you do bring up an interesting point. While I haven't seen that problem arise with any of our other deprecations, I don't see why we shouldn't discuss it. |
@jorisvandenbossche : I opened #17828 to address your point about function argument deprecations. |
I disagree with not raising for the default value is how it is typically done. I think it is rather the other way around (we normally put the deprecated one at None, to be able to distinguish the default and an actual user passed value), but will answer on the issue you created. |
xref #17060 (comment)