Author sahilmn
Recipients ronaldoussoren, sahilmn
Date 2018-05-21.21:08:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAG+dY-vjqN+QL0f8v+Wr3oRFF99WfgxT4eUYPViPAPNRxxGE6g@mail.gmail.com>
In-reply-to <1526890488.51.0.682650639539.issue33590@psf.upfronthosting.co.za>
Content
The task schedule is executed when `s.run()` is called. There should be a
*delay = 5*  from the time the scheduling statement is executed.

If your claim is true, the priority argument is useless since it has no
impact on the execution order when `delay` values are equal. Clearly, this
is not the case since the example for `enter` at
https://docs.python.org/3/library/sched.html aims to demonstrate the use of
`priority` argument.

On Mon, May 21, 2018 at 4:14 AM, Ronald Oussoren <report@bugs.python.org>
wrote:

>
> Ronald Oussoren <ronaldoussoren@mac.com> added the comment:
>
> I don't think  there's a bug here: sched.enter schedules an event some
> time after the current time. The two calls to sched.enter are not at the
> same time, hence the priority is not used because the events are scheduled
> at different times.
>
> ----------
> nosy: +ronaldoussoren
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue33590>
> _______________________________________
>
History
Date User Action Args
2018-05-21 21:08:54sahilmnsetrecipients: + sahilmn, ronaldoussoren
2018-05-21 21:08:54sahilmnlinkissue33590 messages
2018-05-21 21:08:54sahilmncreate