Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
BUG: QuarterBegin doesn't match other offsets for n=0 #11406
Comments
|
I recall this from a discussion within one of the freq issues (though don't remember the substance) |
|
haven't found much yet, but I guess this behavior was explicitly tested - |
chris-b1
referenced
this issue
Oct 24, 2015
Merged
BUG: vectorized DateOffset match non-vectorized #11427
jreback
added Frequency Timeseries API Design
labels
Nov 13, 2015
|
@chris-b1 yeh at the very least quarters should be consistent. I'd say go with how month/year work. Make a nice big note in what's new / docs w.r.t. this as its an API breaking change. |
jreback
added this to the
0.18.0
milestone
Dec 1, 2015
chris-b1
added a commit
to chris-b1/pandas
that referenced
this issue
Dec 6, 2015
|
|
chris-b1 |
08245c8
|
jreback
added a commit
that referenced
this issue
Dec 10, 2015
|
|
chris-b1 + jreback |
56fd4e3
|
|
closed by #11777 |
jreback
closed this
Dec 10, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
chris-b1 commentedOct 22, 2015
xref #8435 (different issue though)
normally the semantic is to roll forward to the next period for
n=0