This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sahilmn
Recipients ronaldoussoren, sahilmn
Date 2018-05-21.21:08:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
The task schedule is executed when `` 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 aims to demonstrate the use of
`priority` argument.

On Mon, May 21, 2018 at 4:14 AM, Ronald Oussoren <>

> Ronald Oussoren <> 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 <>
> <>
> _______________________________________
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