The behavior of `multithreading.Queue.empty()` when the Queue is closed is not explained in the docs

[marcoslimagon]

Documentation

https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Queue.empty

It should be added that in case of the given method Queue.empty() is called after Queue.close() it will raise `OSError("handle is closed")``
(A clear and concise description of the issue.)

Linked PRs

• gh-120012: clarify the behaviour of multiprocessing.Queue.empty on closed queues. #120102
• [3.13] gh-120012: clarify the behaviour of multiprocessing.Queue.empty on closed queues. (GH-120102) #120469
• [3.12] gh-120012: clarify the behaviour of multiprocessing.Queue.empty on closed queues. (GH-120102) #120470

[ericvsmith]

That seems like a good change. I don't think we would typically include the error text in the docs, but the fact that it raises OSError in that case is worth noting.

[rok]

This seems to have been resolved by #120102.