The upcoming panads=1.5 release contains several deprecations around pandas use of numeric_only (xref pandas-dev/pandas#46560). All of these changes are backwards compatible, so user code shouldn't break, but users will start getting lots of deprecation warnings from dasks internal use of pandas (which is scattered throughout dask.dataframe). Ideally, dask would emit the same deprecation pandas does and users wouldn't see any deprecations due to dasks internal use of pandas.

There have been a few attempts at adding numeric_only compatibility to dask with pandas=1.5 (#9269, #9271, #9241) but, as @rhshadrach highlights in pandas-dev/pandas#46560 (comment), exactly what the current default value is for numeric_only and when a deprecation warning isn't super straightforward.

Opening a dedicated issue so we don't loose track of this issue.

cc @rhshadrach as he appears to be leading the numeric_only changes upstream in pandas
cc @mroeschke @jorisvandenbossche in case you have thoughts