[issue21367] multiprocessing.JoinableQueue requires new kwarg

Changes by Berker Peksag : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Cryptic error when subclassing multiprocessing classes ___ Python tracker _

[issue21367] multiprocessing.JoinableQueue requires new kwarg

larkost added the comment: We just got bitten by this issue because we are trying to be compatible across 2.x and 3.x (including 3.0-3.2). For anyone who runs into the "missing 1 required keyword-only argument: 'ctx'" here is an import statement that works: try: from multiprocessing import

[issue21367] multiprocessing.JoinableQueue requires new kwarg

Changes by Dan O'Reilly : -- components: +Library (Lib) -Interpreter Core type: compile error -> behavior ___ Python tracker ___ ___ P

[issue21367] multiprocessing.JoinableQueue requires new kwarg

Dan O'Reilly added the comment: How are you importing JoinableQueue? You'll see this error if you import it from multiprocessing.queues instead of directly from multiprocessing. This is because multiprocessing.JoinableQueue is now a function: def JoinableQueue(self, maxsize=0): ''

[issue21367] multiprocessing.JoinableQueue requires new kwarg

Changes by Claudiu.Popa : -- nosy: +sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue21367] multiprocessing.JoinableQueue requires new kwarg

Lee Clemens added the comment: Same issue (ctx keyword) occurs with multiprocessing.queues.SimpleQueue -- ___ Python tracker ___ ___ P

[issue21367] multiprocessing.JoinableQueue requires new kwarg

New submission from Lee Clemens: Not mentioned (at least not specifically) in the release notes, multiprocessing.JoinableQueue now requires 'ctx' keyword argument: def __init__(self, maxsize=0, *, ctx): This causes an application calling JoinableQueue() to work with 3.3.2 (my single test) to