đź’Ą TRENDING: ./c api/arg.html - Full Archive
Parsing arguments and building values¶
These functions are useful when creating your own extensions functions and methods. Additional information and examples are available in Extending and Embedding the Python Interpreter.
The first three of these functions described, PyArg_ParseTuple(),
PyArg_ParseTupleAndKeywords(), and PyArg_Parse(), all use format
strings which are used to tell the function about the expected arguments. The
format strings use the same syntax for each of these functions.
Parsing arguments¶
A format string consists of zero or more “format units.” A format unit describes one Python object; it is usually a single character or a parenthesized sequence of format units. With a few exceptions, a format unit that is not a parenthesized sequence normally corresponds to a single address argument to these functions. In the following description, the quoted form is the format unit; the entry in (round) parentheses is the Python object type that matches the format unit; and the entry in [square] brackets is the type of the C variable(s) whose address should be passed.
Strings and buffers¶
These formats allow accessing an object as a contiguous chunk of memory. You don’t have to provide raw storage for the returned unicode or bytes area.
In general, when a format sets a pointer to a buffer, the buffer is
managed by the corresponding Python object, and the buffer shares
the lifetime of this object. You won’t have to release any memory yourself.
The only exceptions are es, es#, et and et#.
However, when a Py_buffer structure gets filled, the underlying
buffer is locked so that the caller can subsequently use the buffer even
inside a Py_BEGIN_ALLOW_THREADS block without the risk of mutable data
being resized or destroyed. As a result, you have to call
PyBuffer_Release() after you have finished processing the data (or
in any early abort case).
Unless otherwise stated, buffers are not NUL-terminated.
Some formats require a read-only bytes-like object, and set a
pointer instead of a buffer structure. They work by checking that
the object’s PyBufferProcs.bf_releasebuffer field is NULL,
which disallows mutable objects such as bytearray.
Note
For all # variants of formats (s#, y#, etc.), the type of
the length argument (int or Py_ssize_t) is controlled by
defining the macro PY_SSIZE_T_CLEAN before including
Python.h. If the macro was defined, length is a
Py_ssize_t rather than an int. This behavior will change
in a future Python version to only support Py_ssize_t and
drop int support. It is best to always define PY_SSIZE_T_CLEAN.
s(str) [const char *]Convert a Unicode object to a C pointer to a character string. A pointer to an existing string is stored in the character pointer variable whose address you pass. The C string is NUL-terminated. The Python string must not contain embedded null code points; if it does, a
ValueErrorexception is raised. Unicode objects are converted to C strings using'utf-8'encoding. If this conversion fails, aUnicodeErroris raised.Note
This format does not accept bytes-like objects. If you want to accept filesystem paths and convert them to C character strings, it is preferable to use the
O&format withPyUnicode_FSConverter()as converter.Changed in version 3.5: Previously,
TypeErrorwas raised when embedded null code points were encountered in the Python string.s*(stror bytes-like object) [Py_buffer]This format accepts Unicode objects as well as bytes-like objects. It fills a
Py_bufferstructure provided by the caller. In this case the resulting C string may contain embedded NUL bytes. Unicode objects are converted to C strings using'utf-8'encoding.s#(str, read-only bytes-like object) [const char *, int orPy_ssize_t]Like
s*, except that it doesn’t accept mutable objects. The result is stored into two C variables, the first one a pointer to a C string, the second one its length. The string may contain embedded null bytes. Unicode objects are converted to C strings using'utf-8'encoding.z(strorNone) [const char *]Like
s, but the Python object may also beNone, in which case the C pointer is set to NULL.z*(str, bytes-like object orNone) [Py_buffer]Like
s*, but the Python object may also beNone, in which case thebufmember of thePy_bufferstructure is set to NULL.z#(str, read-only bytes-like object orNone) [const char *, int]Like
s#, but the Python object may also beNone, in which case the C pointer is set to NULL.y(read-only bytes-like object) [const char *]This format converts a bytes-like object to a C pointer to a character string; it does not accept Unicode objects. The bytes buffer must not contain embedded null bytes; if it does, a
ValueErrorexception is raised.Changed in version 3.5: Previously,
TypeErrorwas raised when embedded null bytes were encountered in the bytes buffer.y*(bytes-like object) [Py_buffer]This variant on
s*doesn’t accept Unicode objects, only bytes-like objects. This is the recommended way to accept binary data.y#(read-only bytes-like object) [const char *, int]This variant on
s#doesn’t accept Unicode objects, only bytes-like objects.S(bytes) [PyBytesObject *]Requires that the Python object is a
bytesobject, without attempting any conversion. RaisesTypeErrorif the object is not a bytes object. The C variable may also be declared asPyObject*.Y(bytearray) [PyByteArrayObject *]Requires that the Python object is a
bytearrayobject, without attempting any conversion. RaisesTypeErrorif the object is not abytearrayobject. The C variable may also be declared asPyObject*.u(str) [Py_UNICODE *]Convert a Python Unicode object to a C pointer to a NUL-terminated buffer of Unicode characters. You must pass the address of a
Py_UNICODEpointer variable, which will be filled with the pointer to an existing Unicode buffer. Please note that the width of aPy_UNICODEcharacter depends on compilation options (it is either 16 or 32 bits). The Python string must not contain embedded null code points; if it does, aValueErrorexception is raised.Changed in version 3.5: Previously,
TypeErrorwas raised when embedded null code points were encountered in the Python string.Deprecated since version 3.3, will be removed in version 4.0: Part of the old-style
Py_UNICODEAPI; please migrate to usingPyUnicode_AsWideCharString().u#(str) [Py_UNICODE *, int]This variant on
ustores into two C variables, the first one a pointer to a Unicode data buffer, the second one its length. This variant allows null code points.Deprecated since version 3.3, will be removed in version 4.0: Part of the old-style
Py_UNICODEAPI; please migrate to usingPyUnicode_AsWideCharString().Z(strorNone) [Py_UNICODE *]Like
u, but the Python object may also beNone, in which case thePy_UNICODEpointer is set to NULL.Deprecated since version 3.3, will be removed in version 4.0: Part of the old-style
Py_UNICODEAPI; please migrate to usingPyUnicode_AsWideCharString().Z#(strorNone) [Py_UNICODE *, int]Like
u#, but the Python object may also beNone, in which case thePy_UNICODEpointer is set to NULL.Deprecated since version 3.3, will be removed in version 4.0: Part of the old-style
Py_UNICODEAPI; please migrate to usingPyUnicode_AsWideCharString().U(str) [PyObject *]Requires that the Python object is a Unicode object, without attempting any conversion. Raises
TypeErrorif the object is not a Unicode object. The C variable may also be declared asPyObject*.w*(read-write bytes-like object) [Py_buffer]This format accepts any object which implements the read-write buffer interface. It fills a
Py_bufferstructure provided by the caller. The buffer may contain embedded null bytes. The caller have to callPyBuffer_Release()when it is done with the buffer.es(str) [const char *encoding, char **buffer]This variant on
sis used for encoding Unicode into a character buffer. It only works for encoded data without embedded NUL bytes.This format requires two arguments. The first is only used as input, and must be a
const char*which points to the name of an encoding as a NUL-terminated string, or NULL, in which case'utf-8'encoding is used. An exception is raised if the named encoding is not known to Python. The second argument must be achar**; the value of the pointer it references will be set to a buffer with the contents of the argument text. The text will be encoded in the encoding specified by the first argument.PyArg_ParseTuple()will allocate a buffer of the needed size, copy the encoded data into this buffer and adjust *buffer to reference the newly allocated storage. The caller is responsible for callingPyMem_Free()to free the allocated buffer after use.et(str,bytesorbytearray) [const char *encoding, char **buffer]Same as
esexcept that byte string objects are passed through without recoding them. Instead, the implementation assumes that the byte string object uses the encoding passed in as parameter.es#(str) [const char *encoding, char **buffer, int *buffer_length]This variant on
s#is used for encoding Unicode into a character buffer. Unlike theesformat, this variant allows input data which contains NUL characters.It requires three arguments. The first is only used as input, and must be a
const char*which points to the name of an encoding as a NUL-terminated string, or NULL, in which case'utf-8'encoding is used. An exception is raised if the named encoding is not known to Python. The second argument must be achar**; the value of the pointer it references will be set to a buffer with the contents of the argument text. The text will be encoded in the encoding specified by the first argument. The third argument must be a pointer to an integer; the referenced integer will be set to the number of bytes in the output buffer.There are two modes of operation:
If *buffer points a NULL pointer, the function will allocate a buffer of the needed size, copy the encoded data into this buffer and set *buffer to reference the newly allocated storage. The caller is responsible for calling
PyMem_Free()to free the allocated buffer after usage.If *buffer points to a non-NULL pointer (an already allocated buffer),
PyArg_ParseTuple()will use this location as the buffer and interpret the initial value of *buffer_length as the buffer size. It will then copy the encoded data into the buffer and NUL-terminate it. If the buffer is not large enough, aValueErrorwill be set.In both cases, *buffer_length is set to the length of the encoded data without the trailing NUL byte.
et#(str,bytesorbytearray) [const char *encoding, char **buffer, int *buffer_length]Same as
es#except that byte string objects are passed through without recoding them. Instead, the implementation assumes that the byte string object uses the encoding passed in as parameter.
Numbers¶
b(int) [unsigned char]Convert a nonnegative Python integer to an unsigned tiny int, stored in a C
unsigned char.B(int) [unsigned char]Convert a Python integer to a tiny int without overflow checking, stored in a C
unsigned char.h(int) [short int]Convert a Python integer to a C
short int.H(int) [unsigned short int]Convert a Python integer to a C
unsigned short int, without overflow checking.i(int) [int]Convert a Python integer to a plain C
int.I(int) [unsigned int]Convert a Python integer to a C
unsigned int, without overflow checking.l(int) [long int]Convert a Python integer to a C
long int.k(int) [unsigned long]Convert a Python integer to a C
unsigned longwithout overflow checking.L(int) [long long]Convert a Python integer to a C
long long.K(int) [unsigned long long]Convert a Python integer to a C
unsigned long longwithout overflow checking.n(int) [Py_ssize_t]Convert a Python integer to a C
Py_ssize_t.c(bytesorbytearrayof length 1) [char]Convert a Python byte, represented as a
bytesorbytearrayobject of length 1, to a Cchar.Changed in version 3.3: Allow
bytearrayobjects.C(strof length 1) [int]Convert a Python character, represented as a
strobject of length 1, to a Cint.f(float) [float]Convert a Python floating point number to a C
float.d(float) [double]Convert a Python floating point number to a C
double.D(complex) [Py_complex]Convert a Python complex number to a C
Py_complexstructure.
Other objects¶
O(object) [PyObject *]Store a Python object (without any conversion) in a C object pointer. The C program thus receives the actual object that was passed. The object’s reference count is not increased. The pointer stored is not NULL.
O!(object) [typeobject, PyObject *]Store a Python object in a C object pointer. This is similar to
O, but takes two C arguments: the first is the address of a Python type object, the second is the address of the C variable (of typePyObject*) into which the object pointer is stored. If the Python object does not have the required type,TypeErroris raised.
O&(object) [converter, anything]Convert a Python object to a C variable through a converter function. This takes two arguments: the first is a function, the second is the address of a C variable (of arbitrary type), converted to
void *. The converter function in turn is called as follows:status = converter(object, address);
