Parameter Name of startingMonth for QuarterEnd is Misleading

[cancan101]

startingMonth is the month the quarter ends. This is confusing.

[jtratner]

I don't think this is worth changing - should be using freqstr anyways, right? There's sort of a weird dividing line on offsets about whether the constructors are public or private. I'd prefer to push this to 0.14

[cancan101]

That's fine to push it off. Although I disagree about the constructors
being quasi private.
On Oct 23, 2013 9:49 PM, "Jeff Tratner" [email protected] wrote:

I don't think this is worth changing - should be using freqstr anyways,
right? There's sort of a weird dividing line on offsets about whether the
constructors are public or private. I'd prefer to push this to 0.14

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5307#issuecomment-26961104
.

[mroeschke]

Appears there hasn't been much support for changing this over time. Closing but happy to reopen if there's renewed interest

[WillAyd]

I think this would be nice to fix. I find this API very confusing:

In [133]:   dtype = pd.PeriodDtype(freq=pd.offsets.QuarterEnd(startingMonth=3))
     ...:   pd.Series([
     ...:       "1Q2024",
     ...:       "2Q2024",
     ...:       "3Q2024",
     ...:       "4Q2024",
     ...:   ], dtype=dtype).dt.start_time
Out[133]: 
0   2023-04-01
1   2023-07-01
2   2023-10-01
3   2024-01-01
dtype: datetime64[ns]