Skip to content

[3.13] gh-117291: Explain usage of null bytes in Array(c_char).value (GH-117292) #150651

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
serhiy-storchaka merged 1 commit into from
May 31, 2026
+4 −1
Merged

[3.13] gh-117291: Explain usage of null bytes in Array(c_char).value (GH-117292) #150651

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion Doc/library/multiprocessing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1644,7 +1644,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
Expand Down
Loading