We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the lower part of https://workalendar.github.io/workalendar/basic.html example
>>> cal.add_working_days(datetime(2012, 12, 23, 14, 0, 39), 5) datetime.datetime(2012, 12, 31)
the output is wrongly given, making the following keep_datetime=True option hardly understandable. Actually the result is
keep_datetime=True
datetime.date(2012, 12, 31)
which makes more sense here. ;-)
The text was updated successfully, but these errors were encountered:
indeed. Will fix this, thanks for the bug report.
Sorry, something went wrong.
Doc: Fix the keep_datetime usage example in the "basic" doc
keep_datetime
cd595db
closes #690
89375cd
The documentation bugfix has been included in the latest release of Workalendar, now available on PyPI!
brunobord
Successfully merging a pull request may close this issue.
In the lower part of https://workalendar.github.io/workalendar/basic.html example
the output is wrongly given, making the following
keep_datetime=True
option hardly understandable.Actually the result is
which makes more sense here. ;-)
The text was updated successfully, but these errors were encountered: