Skip to content
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

Year, formerly Y2K compliant, is no longer #46

Open
scruss opened this issue Jan 21, 2024 · 1 comment
Open

Year, formerly Y2K compliant, is no longer #46

scruss opened this issue Jan 21, 2024 · 1 comment

Comments

@scruss
Copy link

scruss commented Jan 21, 2024

Docs say:

y [YYYY]      Set the target Year to calculate for. 2000 to 2099.

However:

sunwait report 43.70011N 79.4163W d 21 m 1 y 2024
Error: "Year" must be between 0 and 99: 2024

As noted in many other issues, the date is off by one, always.

I still think your last version from ~2004 is far preferable to any later "improvements": https://web.archive.org/web/20130202223741/http://www.risacher.org/sunwait/

@treymd
Copy link

treymd commented Apr 4, 2024

I have to rewrite my scripts that calculate dates and times to run my indoor garden due this change. Not sure why a 2 digit year was chosen but alas.... To the author: development whims have consequences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants