-
-
Notifications
You must be signed in to change notification settings - Fork 19k
Closed
Labels
API DesignDatetimeDatetime data dtypeDatetime data dtypeDeprecateFunctionality to remove in pandasFunctionality to remove in pandasUsage Question
Milestone
Description
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.
from pandas.tseries.frequencies import get_offset
get_offset('30s')
or if in statsmodels we should accept custom offsets in place of frequency strings.
Metadata
Metadata
Assignees
Labels
API DesignDatetimeDatetime data dtypeDatetime data dtypeDeprecateFunctionality to remove in pandasFunctionality to remove in pandasUsage Question
Type
Projects
Relationships
Development
Select code repository
Activity
hayd commentedon Jul 11, 2013
Perhaps poor implementation (seems very hacky), but perhaps something like:
should be done on the pandas side.
jseabold commentedon Jul 11, 2013
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.
jreback commentedon Jul 11, 2013
All kinds of goodies in there.....is this in the docs?
jreback commentedon Jul 11, 2013
jseabold commentedon Jul 11, 2013
Ah, great. Any need to keep these functions separate? get_ seems like a subset of to_ to me (without looking at the source).
jreback commentedon Jul 11, 2013
that sounds right.....so changing this issue to deprectate
get_offset
..thxsjbrockmendel commentedon Dec 11, 2019
This isn't exposed in tseries.api or anywhere, does it actually need to be deprecated? could privatize?