Repository navigation
docs: clarify weekday interval restrictions - #668
Open
Hugohong258 wants to merge 1 commit into
Open
Hugohong258 wants to merge 1 commit into
Hugohong258 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The neighboring examples for
every(3).weeksand weekday selection can suggest that these forms can be combined. Clarify that weekday properties such as.mondayrequire a one-week interval and raiseIntervalErrorwith larger intervals. Show the supported two-week form and explain that its first run is two weeks after registration.Related to #556 and #613. This documents the existing restriction; it does not add biweekly weekday selection.
Validation: 17 checks against the current source cover two-week scheduling, all seven weekdays with two- and three-week intervals, and ordinary weekly scheduling. The Sphinx HTML build passes with warnings treated as errors. The full
test_schedule.pysuite cannot collect on Windows because its existing module-leveltime.tzset()call is unavailable; no runtime or test files are changed.