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

[Matthew Fisher]

Matthew Fisher <mfisher at klarisdx.com> added the comment:

> I did look at the code :-)

I also looked at the code.  I had to do so to understand why the example output was not "as expected."  ;)

> I don't agree about the example in the documentation, it is a clear
> demonstration about how to use the API in general and AFAIK is not
> intended to show how priorities work.

Although I came to the same conclusion as you regarding both the fact and the reason the output was correct, I respectfully disagree that the example is clear.  It is not.  Yes, the example, as written, is intended to demonstrate the API -- which consists of several functionalities *including priority*.  If this were not so, the example would not be passing different priority values with the same delay value.

I suggest re-opening this issue as a documentation bug and modifying the example to use enterabs instead of enter.

Respectfully,
M Fisher

----------
nosy: +mfisher

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