[issue11675] multiprocessing Arrays not automatically zeroed.

Mark Dickinson report at bugs.python.org
Fri Mar 25 22:02:05 CET 2011


New submission from Mark Dickinson <dickinsm at gmail.com>:

The documentation for the multiprocessing module says:

"If size_or_initializer is an integer, then it determines the length of the array, and the array will be initially zeroed. "

But the part about the array being zeroed doesn't seem to be true:

Python 3.3a0 (default:03c7a83bbdd3, Mar 25 2011, 21:00:37) 
[GCC 4.2.1 (Apple Inc. build 5664)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from multiprocessing import Array
[67297 refs]
>>> arr1 = Array('i', [56, 27, 1729])
[79877 refs]
>>> del arr1
[79805 refs]
>>> arr2 = Array('i', 3)
[79876 refs]
>>> list(arr2)  # expect [0, 0, 0]
[56, 27, 1729]
[79882 refs]

----------
components: Library (Lib)
messages: 132153
nosy: jnoller, mark.dickinson
priority: normal
severity: normal
status: open
title: multiprocessing Arrays not automatically zeroed.
type: behavior
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3

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


More information about the Python-bugs-list mailing list