These functions raise TypeError when expecting a bytes parameter and
called with a non-bytes parameter.
CPython implementation detail: The internal buffer of PyBytesObject always includes an extra
trailing null byte for compatibility with null terminated C strings.
This extra byte is not counted in PyBytes_Size() nor in the
various length and size arguments of the functions below.
Return value: New reference. Part of the Stable ABI. Thread safety: Atomic.
Return a new bytes object with a copy of the string v as value on success,
and NULL on failure. The parameter v must not be NULL; it will not be
checked.
Return value: New reference. Part of the Stable ABI. Thread safety: Atomic.
Return a new bytes object with a copy of the string v as value and length
len on success, and NULL on failure. If v is NULL, the contents of
the bytes object are uninitialized.
Return value: New reference. Part of the Stable ABI. Thread safety: Atomic.
Take a C printf()-style format string and a variable number of
arguments, calculate the size of the resulting Python bytes object and return
a bytes object with the values formatted into it. The variable arguments
must be C types and must correspond exactly to the format characters in the
format string. The following format characters are allowed:
The hex representation of a C
pointer. Mostly equivalent to
printf("%p") except that
it is guaranteed to start with
the literal 0x regardless
of what the platform’s
printf yields.
An unrecognized format character causes all the rest of the format string to be
copied as-is to the result object, and any extra arguments discarded.
Return a pointer to the contents of o. The pointer
refers to the internal buffer of o, which consists of len(o)+1
bytes. The last byte in the buffer is always null, regardless of
whether there are any other null bytes. The data must not be
modified in any way, unless the object was just created using
PyBytes_FromStringAndSize(NULL,size). It must not be deallocated. If
o is not a bytes object at all, PyBytes_AsString() returns NULL
and raises TypeError.
Return the null-terminated contents of the object obj
through the output variables buffer and length.
Returns 0 on success.
If length is NULL, the bytes object
may not contain embedded null bytes;
if it does, the function returns -1 and a ValueError is raised.
The buffer refers to an internal buffer of obj, which includes an
additional null byte at the end (not counted in length). The data
must not be modified in any way, unless the object was just created using
PyBytes_FromStringAndSize(NULL,size). It must not be deallocated. If
obj is not a bytes object at all, PyBytes_AsStringAndSize()
returns -1 and raises TypeError.
Changed in version 3.5: Previously, TypeError was raised when embedded null bytes were
encountered in the bytes object.
Create a new bytes object in *bytes containing the contents of newpart
appended to bytes; the caller will own the new reference.
The reference to the old value of bytes will be “stolen”.
If the new object cannot be created, the old reference to bytes will still
be “stolen”, the value of *bytes will be set to NULL, and
the appropriate exception will be set.
Note
If newpart implements the buffer protocol, then the buffer
must not be mutated while the new bytes object is being created.
Create a new bytes object in *bytes containing the contents of newpart
appended to bytes. This version releases the strong reference
to newpart (i.e. decrements its reference count).
Note
If newpart implements the buffer protocol, then the buffer
must not be mutated while the new bytes object is being created.
sep must be Python bytes object.
(Note that PyUnicode_Join() accepts NULL separator and treats
it as a space, whereas PyBytes_Join() doesn’t accept NULL
separator.)
iterable must be an iterable object yielding objects that implement the
buffer protocol.
On success, return a new bytes object.
On error, set an exception and return NULL.
Added in version 3.14.
Note
If iterable objects implement the buffer protocol, then the buffers
must not be mutated while the new bytes object is being created.
Resize a bytes object. newsize will be the new length of the bytes object.
You can think of it as creating a new bytes object and destroying the old
one, only more efficiently.
Pass the address of an
existing bytes object as an lvalue (it may be written into), and the new size
desired. On success, *bytes holds the resized bytes object and 0 is
returned; the address in *bytes may differ from its input value. If the
reallocation fails, the original bytes object at *bytes is deallocated,
*bytes is set to NULL, MemoryError is set, and -1 is
returned.
While bytes objects are usually immutable in Python, this special C API
allows mutating a bytes object in-place. The returned bytes object can still
be mutated using PyBytes_AsString(); except if newsize is
zero in which case it returns the immutable empty bytes string.
Get the string representation of bytes. This function is currently used to
implement bytes.__repr__() in Python.
This function does not do type checking; it is undefined behavior to pass
bytes as a non-bytes object or NULL.
If smartquotes is true, the representation will use a double-quoted string
instead of single-quoted string when single-quotes are present in bytes.
For example, the byte string 'Python' would be represented as
b"'Python'" when smartquotes is true, or b'\'Python\'' when it is
false.
On success, this function returns a strong reference to a
str object containing the representation. On failure, this
returns NULL with an exception set.
Unescape a backslash-escaped string s. s must not be NULL.
len must be the size of s.
errors must be one of "strict", "replace", or "ignore". If
errors is NULL, then "strict" is used by default.
On success, this function returns a strong reference to a Python
bytes object containing the unescaped string. On failure, this
function returns NULL with an exception set.
Changed in version 3.9: unicode and recode_encoding are now unused.
If size is greater than zero, allocate size bytes, and set the
writer size to size. The caller is responsible to write size
bytes using PyBytesWriter_GetData().
This function does not overallocate.
Similar to PyBytes_FromFormat(), but write the output directly at
the writer end. Grow the writer internal buffer on demand. Then add the
written size to the writer size.
On success, return 0.
On error, set an exception and return -1.
Resize the writer to size bytes. It can be used to enlarge or to
shrink the writer.
This function typically overallocates to achieve amortized performance when
resizing multiple times.
Newly allocated bytes are left uninitialized.
On success, return 0.
On error, set an exception and return -1.
Resize the writer by adding grow bytes to the current writer size.
This function typically overallocates to achieve amortized performance when
resizing multiple times.
Newly allocated bytes are left uninitialized.
On success, return 0.
On error, set an exception and return -1.
Example of code using the soft deprecated _PyBytes_Resize() API:
PyObject*create_string(Py_ssize_tsize){PyObject*bytes=PyBytes_FromStringAndSize(NULL,size);if(bytes==NULL){returnNULL;}char*str=PyBytes_AS_STRING(bytes);// ... write data into str ...if(_PyBytes_Resize(&bytes,(str-PyBytes_AS_STRING(bytes)))){returnNULL;}returnbytes;}
It can now be updated to:
PyObject*create_string(Py_ssize_tsize){PyBytesWriter*writer=PyBytesWriter_Create(size);if(writer==NULL){returnNULL;}char*str=PyBytesWriter_GetData(writer);// ... write data into str ...returnPyBytesWriter_FinishWithPointer(writer,str);}
The Python Software Foundation is a non-profit corporation.
Please donate.
Last updated on Nov 12, 2026 (18:57 UTC).
Found a bug?
Created using Sphinx 9.1.1.
You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.