[issue45311] Threading Semaphore and BoundedSemaphore release method implementation improvement

Serhiy Storchaka added the comment: This code was added in bpo-10978. Raymond, what are your thoughts? -- nosy: +rhettinger versions: +Python 3.11 -Python 3.9 ___ Python tracker

[issue45311] Threading Semaphore and BoundedSemaphore release method implementation improvement

Besart Dollma added the comment: This is another illogical behaviour, if I am trying to release 5 threads, and I fail the releasing the first one, why should I try the first one 5 times? -- ___ Python tracker

[issue45311] Threading Semaphore and BoundedSemaphore release method implementation improvement

Change by Ken Jin : -- nosy: +pitrou, serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45311] Threading Semaphore and BoundedSemaphore release method implementation improvement

Change by Andrei Kulakov : -- nosy: +kj ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45311] Threading Semaphore and BoundedSemaphore release method implementation improvement

Andrei Kulakov added the comment: Besart: with the current code, if there's a valueError when releasing a thread, it will be retried again n times, with your change, n waiting threads will be released, even if some of them fail with ValueError. I don't know enough about threading module to

[issue45311] Threading Semaphore and BoundedSemaphore release method implementation improvement

New submission from Besart Dollma : Hi, I was looking at the implementation of Semaphore and BoundedSemaphore in threading.py and I saw that `notify` is called on a loop n times while it supports an n parameter.