DEPR: back-compat shim for select_dtypes #62718
Merged
+51
−10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pandas/core/frame.py
Outdated
| # GH#61916 | ||
| warnings.warn( | ||
| "For backward compatibility, 'str' dtypes are included by " | ||
| "select_dtypes when object dtypes are specified. " |
There was a problem hiding this comment.
Suggested change
| "select_dtypes when object dtypes are specified. " | |
| "select_dtypes when 'object' dtype is specified. " |
Comment on lines
2375
to
2380
| To select string columns include ``str``: | ||
|
|
||
| .. ipython:: python | ||
| df.select_dtypes(include=["object"]) | ||
| df.select_dtypes(include=[str]) | ||
There was a problem hiding this comment.
I would maybe add a note that this changed in pandas 3.0 and that for pandas<3, include="object" was used. Maybe with a link to https://pandas.pydata.org/docs/user_guide/migration-3-strings.html#hardcoded-use-of-object-dtype
There was a problem hiding this comment.
Good idea, updated.
jorisvandenbossche
approved these changes
Oct 19, 2025
| .. note:: | ||
|
|
||
| This is a change in pandas 3.0. Previously strings were stored in ``object`` dtype columns, so would be selected with ``include=[object]``. See https://pandas.pydata.org/docs/user_guide/migration-3-strings.html#hardcoded-use-of-object-dtype. |
There was a problem hiding this comment.
Suggested change
| This is a change in pandas 3.0. Previously strings were stored in ``object`` dtype columns, so would be selected with ``include=[object]``. See https://pandas.pydata.org/docs/user_guide/migration-3-strings.html#hardcoded-use-of-object-dtype. | |
| This is a change in pandas 3.0. Previously strings were stored in ``object`` dtype columns, so would be selected with ``include=[object]``. See :ref:`string_migration.object`. |
Best to use internal references for something like this (but will do this in a follow-up PR expanding that section a bit)
There was a problem hiding this comment.
The migration guide actually already had the content, but so just updating the reference, and also added a link to the depr warning -> #62759
|
@jbrockmendel thanks! |
40 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
select_dtypes#61916 (Replace xxxx with the GitHub issue number)doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.cc @jorisvandenbossche