dask: Upstream test failures

I think these are all just FutureWarnings coming from pandas. I’ll try to take a look this week or next.

From: https://github.com/dask/dask/runs/2795401230

Here’s the breakdown AFAICT

6: FutureWarning: The 'freq' argument in Timestamp is deprecated and will be removed in a future version. 24: FutureWarning: In a future version of pandas all arguments of concat except for the argument 'objs' will be keyword-only 12: FutureWarning: In a future version of pandas all arguments of DataFrame.drop except for the argument 'labels' will be keyword-only

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 17 (13 by maintainers)

Most upvoted comments

Yes, we will ensure to fix that on the pandas side before the final 1.3 release.

jorisvandenbossche on Jun 14, 2021

Ah right, didn’t see I was in the wrong project 😅

rwijtvliet on Jan 21, 2022

I opened https://github.com/pandas-dev/pandas/issues/41949 to keep track of fixing the unpickle on the pandas side

I think the best thing from our end would be to not include the freq when selecting from a DatetimeIndex is that possible?

I’d be happy to see that change, but its an API change so i expect there would be pushback about doing it without the deprecation.

@jsignell what do you actually mean exactly with “include the freq when selecting from a DatetimeIndex”?

You mean that if you slice a Series/DataFrame that has a DatetimeIndex with Timestamp objects, like s[Timestamp(..):Timestamp(..)] ?

jorisvandenbossche on Jun 11, 2021