-
-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
ERR: Most consistent error handling when passing win_type='freq' in rolling #15969
Comments
In the spirit of #15836, I'd be inclined to disallow case 2, although certainly should raise a better error message. |
Hmm, yeah I probably agree.
I've updated the original post to have the traceback with scipy installed. Now it's |
this is a dupe of #15584 and case 2 should not be supported. |
actually these all work (except case 2), except that specifying |
I'll re-open but what is the justification for directly supporting |
Right, win_type is the issue. The use-case is making the dask implementation a bit easier. Not super difficult to work around. And I was just surprised that In [16]: s.rolling('2s')
Out[16]: Rolling [window=2000000000,min_periods=1,center=False,win_type=freq,axis=0]
In [17]: s.rolling('2s', win_type='freq') # TypeError went down different code-paths. Not a big deal though. |
Can we change the |
Yeah, I'm fine with that, rather than allowing a user to specify |
Working on dask/dask#2190 (df.rolling('5s') for dask), and I think these should all be equivalent.
I don't think there are any parsing ambiguities.
Currently we have
The text was updated successfully, but these errors were encountered: