[issue33590] sched.enter priority has no impact on execution

[sahilmn]

sahilmn <sahilmanocha1994 at gmail.com> added the comment:

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 at bugs.python.org>
wrote:

>
> Ronald Oussoren <ronaldoussoren at 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 at bugs.python.org>
> <https://bugs.python.org/issue33590>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33590>
_______________________________________