-
Notifications
You must be signed in to change notification settings - Fork 14
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
Support February 29 month end date for leap year #20
Comments
Interesting, I didn't realize that someone might want to use a leap day/month in this way. I wonder if we should just change 2001 to be a leap year. That would keep the code simple but also allow for this behavior. Thoughts? |
Also, the logic you pointed out is only used to define the start of a fiscal calendar, not the end. Isn't is already possible to have a fiscal calendar that ends on Fed 29th? |
If I understand the thread correctly, yes it does seem you can already have a fiscal year that ends on Feb 29th.
Additional thought: We could consider adding an explicit error case for anyone attempting to call it with those parameters (i.e. |
Where I initially came across this is the data I'm working with gives fiscal year end not start. From looking through the 10-k/q's etc filed with the SEC, all of them (that I've looked through) give the date for the period ending. Perhaps this issue is better approached by being able to initialize a fiscal calendar with a period ending year/month/day? Just a thought given how the SEC financial reports are organized/reported. |
Yes, we could definitely modify |
Some companies use February for their end month for the fiscal year e.g. CarMax and their 10-K with last day as Feb 29, 2016 https://www.sec.gov/Archives/edgar/data/0001170010/000117001016000117/kmx0229201610-k.htm
Currently
_check_day
use2001
a non-leap year to validate the day of the month:Resolution would be to use
year
if provided e.g.Note, in this example, changed order of args (for OCD purposes :) with year last as optional
The text was updated successfully, but these errors were encountered: