[New-bugs-announce] [issue25201] lock of multiprocessing.Value is not a keyword-only argument

Berker Peksag report at bugs.python.org
Mon Sep 21 06:05:21 CEST 2015


New submission from Berker Peksag:

>From https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Value

    Note that lock is a keyword-only argument.

But the signature of Value (in Lib/multiprocessing/context.py)

    def Value(self, typecode_or_type, *args, lock=True):

and (in Lib/multiprocessing/sharedctypes.py)

    def Value(typecode_or_type, *args, lock=True, ctx=None):

I'd suggest to remove that part of the documentation in 3.4+. We can also make it a keyword-only argument in Python 3.6. That will make the API more similar with https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Array

----------
assignee: docs at python
components: Documentation
messages: 251196
nosy: berker.peksag, davin, docs at python, sbt
priority: normal
severity: normal
stage: needs patch
status: open
title: lock of multiprocessing.Value is not a keyword-only argument
type: behavior
versions: Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25201>
_______________________________________


More information about the New-bugs-announce mailing list