Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Here is a patch nonetheless. It makes the code match the the documentation:
http://docs.python.org/library/multiprocessing.html#multiprocessing.sharedctypes.Arra y """ - If lock is True (the default) then a new lock object is created to synchronize access to the value. - If lock is a Lock or RLock object then that will be used to synchronize access to the value. - If lock is False then access to the returned object will not be automatically protected by a lock, so it will not necessarily be process-safe. """ I changed multiprocessing.sharedctypes.Array and multiprocessing. sharedctypes.Array I had to change some tests: now "lock=None" is an error. + some markup fixes in the documentation. ---------- keywords: +patch nosy: +amaury.forgeotdarc Added file: http://bugs.python.org/file12204/mp_array.patch _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4449> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
