CLN: refactor block storage selection to use dtype_class._is_numeric #52413
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.
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.Numpy 1.25 will add a new
_is_numeric
attribute on dtype classes that isTrue
for dtypes numpy (and pandas it turns out) considers to be numeric andFalse
otherwise (see numpy/numpy#23190):Besides clarity and avoiding the cryptic
dtype.kind
codes, this change makes it possible for pandas to ingest numpy dtypes written using the currently experimental NEP 42 dtype API, in particular the new string dtype I'm working on (see #47884).Note that this isn't sufficient to get arbitrary new dtypes working or my string dtype, more changes are coming to support that once it's more feasible to upstream the changes along with new tests in pandas, so this is more of a cleanup with an eye towards future new features.