[issue22872] multiprocessing.Queue raises AssertionError

Serhiy Storchaka added the comment: I don't think we need to document AssertionError in older Python versions. This is an implementation detail. We don't document all exceptions that can be raised with improper use of the API. Just don't do this. In addition, using the assert statement for

[issue22872] multiprocessing.Queue raises AssertionError

Serhiy Storchaka added the comment: New changeset 0461704060474cb358d3495322950c4fd00616a0 by Serhiy Storchaka (Zackery Spytz) in branch 'master': bpo-22872: multiprocessing.Queue's put() and get() now raise ValueError if the queue is closed. (GH-9010)

[issue22872] multiprocessing.Queue raises AssertionError

Change by Zackery Spytz : -- nosy: +ZackerySpytz ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22872] multiprocessing.Queue raises AssertionError

Change by Zackery Spytz : -- pull_requests: +8480 stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue22872] multiprocessing.Queue raises AssertionError

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22872] multiprocessing.Queue raises AssertionError

Antoine Pitrou added the comment: The expected behaviour here would be to raise ValueError, as on other closed objects: >>> s = io.StringIO() >>> s.close() >>> s.write("") Traceback (most recent call last): File "", line 1, in ValueError: I/O operation on closed file

[issue22872] multiprocessing.Queue raises AssertionError

Change by Antoine Pitrou : -- components: +Library (Lib) -ctypes ___ Python tracker ___ ___

[issue22872] multiprocessing.Queue raises AssertionError

Change by Jason Qian : -- components: +ctypes -Library (Lib) versions: -Python 3.4, Python 3.5 ___ Python tracker ___

[issue22872] multiprocessing.Queue raises AssertionError

Berker Peksag added the comment: See issue 5001 for more general cleanup in multiprocessing. > [...] (2) altering the behavior in a new release version (perhaps 3.6 when it > comes) and documenting that change appropriately there. +1. We can also document AssertionError in older Python

[issue22872] multiprocessing.Queue raises AssertionError

Davin Potts added the comment: The proposed patch would potentially break existing code which anticipates the current behavior. The potential negative impact means this particular proposed patch is not viable. Choices forward include: (1) better documenting the existing, established

[issue22872] multiprocessing.Queue raises AssertionError

Changes by Ethan Furman et...@stoneleaf.us: -- nosy: -ethan.furman ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22872 ___ ___ Python-bugs-list

[issue22872] multiprocessing.Queue raises AssertionError

Milan Oberkirch added the comment: Here is the trivial patch for that :) -- keywords: +patch nosy: +zvyn Added file: http://bugs.python.org/file39700/issue22872.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22872

[issue22872] multiprocessing.Queue raises AssertionError

Changes by Davin Potts pyt...@discontinuity.net: -- nosy: +davin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22872 ___ ___ Python-bugs-list

[issue22872] multiprocessing.Queue raises AssertionError

New submission from Joseph Siddall: putting something in Queue(multiprocessing.Queue) after closing it raises an AssertionError. Getting something out of a Queue after closing it raises an OSError. I expected both scenarios to raise the same exception. To Reproduce: from multiprocessing

[issue22872] multiprocessing.Queue raises AssertionError

Changes by Ethan Furman et...@stoneleaf.us: -- nosy: +ethan.furman, jnoller, sbt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22872 ___ ___