dbader / dbader/schedule

Unable to schedule from a specific time and following a specific calendar

Open
#597 4 comments 3 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
12.3k
Forks
999
PR merge metrics
No merged PRs in 30d

Description

The library supports scheduling until a certain time but not from time. Consequently, it is difficult to implement logic such as **every hour on Monday-Friday from 11:30 to 12:30**.

We created a custom function that generates a list of options, in this case

- every().monday.at("11:30")
- every().monday.at("12:30")
- every().tuesday.at("12:30")
- ..,
- every().friday.at("12:30")

This implies 15 calls, as opposed to only 5 calls per each day, or just 1 call per calendar that sets Monday to Friday eligible.

With a more frequent schedule, this becomes even more prohibitive. In such a case, we just run the job at **every().minute** and exit early when outside of schedule from job function, i.e. manage schedule externally.

Any enhancements planned? Any idea how to enhance internally the library?

- every().monday.from('11:30').to('12:30')
- every().minute.on(calendar).from('11:30').to('12:30')

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the scheduling API entry points mentioned in the issue: every().monday.at(), every().minute, and the proposed from()/to() and calendar forms. Compare the current “until” support with the requested time-window and weekday-calendar behavior. Done means the library can express the stated schedules without generating one call per time option, with behavior confirmed by appropriate tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.