From: Patrick Rauscher <prauscher@prauscher.de>
Date: Sun, 31 May 2026 07:20:49 +0000 (+0200)
Subject: gh-117291: Explain usage of null bytes in Array(c_char).value (GH-117292)
X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=73d8e9a47cc13ce1b9b1bdfdeaa958639b144f55;p=thirdparty%2FPython%2Fcpython.git

gh-117291: Explain usage of null bytes in Array(c_char).value (GH-117292)
---

diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index 7b17df08f7dc..2d1305391583 100644
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -1723,7 +1723,10 @@ inherited by child processes.
    Note that *lock* is a keyword only argument.
 
    Note that an array of :data:`ctypes.c_char` has *value* and *raw*
-   attributes which allow one to use it to store and retrieve strings.
+   attributes which can both be used to store and retrieve byte strings.
+   While *raw* allows interaction with a :class:`bytes` object the full size of
+   the array, reading *value* will terminate after a null byte, like most
+   programming languages handle strings.
 
 
 The :mod:`!multiprocessing.sharedctypes` module