-
-
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
API: deprecate get_offset, Offset for time rules like '30s' #4205
Comments
Perhaps poor implementation (seems very hacky), but perhaps something like:
should be done on the pandas side. |
That's what I had in mind as long as it's valid for any integer + existing offset. I'll go ahead and add a workaround on our side like this. |
All kinds of goodies in there.....is this in the docs?
|
|
Ah, great. Any need to keep these functions separate? get_ seems like a subset of to_ to me (without looking at the source). |
that sounds right.....so changing this issue to deprectate |
This isn't exposed in tseries.api or anywhere, does it actually need to be deprecated? could privatize? |
From stackoverflow: http://stackoverflow.com/questions/17579932/statsmodel-arma-function-is-incompatiable-with-pandas/17581170
I'm looking only quickly at this, but I'm wondering if this should be recognized and return an offset.
or if in statsmodels we should accept custom offsets in place of frequency strings.
The text was updated successfully, but these errors were encountered: