Schedule task on weekends or workweek

[msoedov]

That's would be very useful and I believe it's pretty common case

[dbader]

Hi @msoedov 👋 I like the general idea but we could run into some trouble finding an international definition of "weekend" vs "workweek":

the weekend in Israel is observed on Friday–Saturday. Some Muslim-majority countries historically had a Thursday–Friday or Friday–Saturday weekend

(https://en.wikipedia.org/wiki/Workweek_and_weekend)

On the other hand I don't want to overcomplicate this either 😃 . My gut feeling would be that it's "safer" to ask people to spell out the schedule explicitly on a day by day basis.

Curious to hear your thoughts though!

~ Dan

[msoedov]

I would suggest to implement "weekend" and "workweek" in the traditional meaning. For those who have exceptional cases like

Thursday–Friday or Friday–Saturday weekend

and believe it going to be less than 1% of users. Those can

spell out the schedule explicitly on a day by day basis.

[gregv21v]

I think it would be pretty easy for people to define their own weekend schedule.

[tompaton]

I would like something that did this for the cases when repeating the arguments to the job is messy.

How about an alternative Job factory (in addition to every()) that works as a generator and returns partially built Job instances. example usage:

for job in schedule.weekdays('monday', 'thursday'):
    job.at('7:45').do(something, arg1, arg2)

weekdays without arguments would default to 'monday', 'tuesday', 'wednesday', 'thursday', 'friday'.

A similar weekends method would default to 'saturday' and 'sunday'.

That would be very concise for the "default" case, and still completely customisable.

For now, I'm going to use the following helper in my project:

def schedule_weekdays(*days):
    for day in (days or ['monday', 'tuesday', 'wednesday', 'thursday', 'friday']):
        job = schedule.every()
        yield getattr(job, day)