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 r.david.murray
Recipients r.david.murray, ronaldoussoren, sahilmn
Date 2018-05-21.21:22:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I think Ronald is correct.

The priority argument for enter would apply if you called enter twice with two different delays, but they happen to end up pointing to the same moment in time from the scheduler's point of view.

How would the computer know that two calls to enter with the same delay are supposed to point to the same moment in time?

But you are correct, it looks like the example would make more sense if it used enterabs, not enter.

You can test our theory by writing time and delay functions with a course enough resolution that two sequential calls to delay will end up pointing to the time time unit.  (Or we could look at the code :)
Date User Action Args
2018-05-21 21:22:19r.david.murraysetrecipients: + r.david.murray, ronaldoussoren, sahilmn
2018-05-21 21:22:19r.david.murraysetmessageid: <>
2018-05-21 21:22:19r.david.murraylinkissue33590 messages
2018-05-21 21:22:19r.david.murraycreate