bpo-22872: multiprocessing.Queue's put() and get() now raise ValueError if the queue is closed by ZackerySpytz · Pull Request #9010 · python/cpython (original) (raw)

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation4 Commits3 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

ZackerySpytz

@ZackerySpytz

…or if the queue is closed

Previously, put() and get() would raise AssertionError and OSError, respectively.

auvipy

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

serhiy-storchaka

def test_closed_queue_put_get_exceptions(self):
for q in multiprocessing.Queue(), multiprocessing.JoinableQueue():
q.close()
for meth, args in (q.put, ('foo',)), (q.get, ()):

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would look clearer (and just one line longer) if unroll this loop.

@bedevere-bot

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@ZackerySpytz

serhiy-storchaka

@serhiy-storchaka