blob: 1b2ab8f843c66dfb6e4538e90dd458becaafab49 [file] [log] [blame]
Georg Brandl54a3faa2008-01-20 09:30:57 +00001.. highlightlang:: c
2
3.. _arg-parsing:
4
5Parsing arguments and building values
6=====================================
7
8These functions are useful when creating your own extensions functions and
9methods. Additional information and examples are available in
10:ref:`extending-index`.
11
12The first three of these functions described, :cfunc:`PyArg_ParseTuple`,
13:cfunc:`PyArg_ParseTupleAndKeywords`, and :cfunc:`PyArg_Parse`, all use *format
14strings* which are used to tell the function about the expected arguments. The
15format strings use the same syntax for each of these functions.
16
17A format string consists of zero or more "format units." A format unit
18describes one Python object; it is usually a single character or a parenthesized
19sequence of format units. With a few exceptions, a format unit that is not a
20parenthesized sequence normally corresponds to a single address argument to
21these functions. In the following description, the quoted form is the format
22unit; the entry in (round) parentheses is the Python object type that matches
23the format unit; and the entry in [square] brackets is the type of the C
24variable(s) whose address should be passed.
25
26``s`` (string or Unicode object) [const char \*]
27 Convert a Python string or Unicode object to a C pointer to a character string.
28 You must not provide storage for the string itself; a pointer to an existing
29 string is stored into the character pointer variable whose address you pass.
30 The C string is NUL-terminated. The Python string must not contain embedded NUL
31 bytes; if it does, a :exc:`TypeError` exception is raised. Unicode objects are
32 converted to C strings using the default encoding. If this conversion fails, a
33 :exc:`UnicodeError` is raised.
34
Benjamin Peterson4469d0c2008-11-30 22:46:23 +000035 Starting with Python 2.5 the type of the length argument can be
36 controlled by defining the macro :cmacro:`PY_SSIZE_T_CLEAN` before
37 including :file:`Python.h`. If the macro is defined, length is a
38 :ctype:`Py_ssize_t` rather than an int.
39
Martin v. Löwis423be952008-08-13 15:53:07 +000040``s*`` (string, Unicode, or any buffer compatible object) [Py_buffer \*]
Georg Brandl8fa89522008-09-01 16:45:35 +000041 This is similar to ``s``, but the code fills a :ctype:`Py_buffer` structure
42 provided by the caller. In this case the Python string may contain embedded
43 null bytes. Unicode objects pass back a pointer to the default encoded
44 string version of the object if such a conversion is possible. The
45 underlying buffer is locked, so that the caller can subsequently use the
46 buffer even inside a ``Py_BEGIN_ALLOW_THREADS`` block. **The caller is
47 responsible** for calling ``PyBuffer_Release`` with the structure after it
48 has processed the data.
49
Gregory P. Smith02c3b5c2008-11-23 23:49:16 +000050``s#`` (string, Unicode or any read buffer compatible object) [const char \*, int or :ctype:`Py_ssize_t`]
Benjamin Peterson4469d0c2008-11-30 22:46:23 +000051 This variant on ``s`` stores into two C variables, the first one a pointer to
52 a character string, the second one its length. In this case the Python
53 string may contain embedded null bytes. Unicode objects pass back a pointer
54 to the default encoded string version of the object if such a conversion is
55 possible. All other read-buffer compatible objects pass back a reference to
56 the raw internal data representation. Since this format doesn't allow writable buffer compatible objects like byte
57 arrays, ``s*`` is to be preferred.
58
59 The type of the length argument (int or :ctype:`Py_ssize_t`) is controlled by
Gregory P. Smith02c3b5c2008-11-23 23:49:16 +000060 defining the macro :cmacro:`PY_SSIZE_T_CLEAN` before including
61 :file:`Python.h`. If the macro was defined, length is a :ctype:`Py_ssize_t`
Benjamin Peterson4469d0c2008-11-30 22:46:23 +000062 rather than an int. This behavior will change in a future Python version to
63 only support :ctype:`Py_ssize_t` and drop int support. It is best to always
64 define :cmacro:`PY_SSIZE_T_CLEAN`.
Martin v. Löwis423be952008-08-13 15:53:07 +000065
Georg Brandl54a3faa2008-01-20 09:30:57 +000066``y`` (bytes object) [const char \*]
Georg Brandl8fa89522008-09-01 16:45:35 +000067 This variant on ``s`` converts a Python bytes or bytearray object to a C
68 pointer to a character string. The bytes object must not contain embedded
69 NUL bytes; if it does, a :exc:`TypeError` exception is raised.
Georg Brandl54a3faa2008-01-20 09:30:57 +000070
Martin v. Löwis423be952008-08-13 15:53:07 +000071``y*`` (bytes object) [Py_buffer \*]
72 This is to ``s*`` as ``y`` is to ``s``.
73
Georg Brandl8fa89522008-09-01 16:45:35 +000074``y#`` (bytes object) [const char \*, int]
75 This variant on ``s#`` stores into two C variables, the first one a pointer
76 to a character string, the second one its length. This only accepts bytes
77 objects, no byte arrays.
78
Georg Brandl54a3faa2008-01-20 09:30:57 +000079``z`` (string or ``None``) [const char \*]
80 Like ``s``, but the Python object may also be ``None``, in which case the C
81 pointer is set to *NULL*.
82
Martin v. Löwis423be952008-08-13 15:53:07 +000083``z*`` (string or ``None`` or any buffer compatible object) [Py_buffer*]
84 This is to ``s*`` as ``z`` is to ``s``.
85
Georg Brandl8fa89522008-09-01 16:45:35 +000086``z#`` (string or ``None`` or any read buffer compatible object) [const char \*, int]
87 This is to ``s#`` as ``z`` is to ``s``.
88
Georg Brandl54a3faa2008-01-20 09:30:57 +000089``u`` (Unicode object) [Py_UNICODE \*]
90 Convert a Python Unicode object to a C pointer to a NUL-terminated buffer of
91 16-bit Unicode (UTF-16) data. As with ``s``, there is no need to provide
92 storage for the Unicode data buffer; a pointer to the existing Unicode data is
93 stored into the :ctype:`Py_UNICODE` pointer variable whose address you pass.
94
95``u#`` (Unicode object) [Py_UNICODE \*, int]
96 This variant on ``u`` stores into two C variables, the first one a pointer to a
97 Unicode data buffer, the second one its length. Non-Unicode objects are handled
98 by interpreting their read-buffer pointer as pointer to a :ctype:`Py_UNICODE`
99 array.
100
101``Z`` (Unicode or ``None``) [Py_UNICODE \*]
102 Like ``s``, but the Python object may also be ``None``, in which case the C
103 pointer is set to *NULL*.
104
105``Z#`` (Unicode or ``None``) [Py_UNICODE \*, int]
106 This is to ``u#`` as ``Z`` is to ``u``.
107
108``es`` (string, Unicode object or character buffer compatible object) [const char \*encoding, char \*\*buffer]
109 This variant on ``s`` is used for encoding Unicode and objects convertible to
110 Unicode into a character buffer. It only works for encoded data without embedded
111 NUL bytes.
112
113 This format requires two arguments. The first is only used as input, and
114 must be a :ctype:`const char\*` which points to the name of an encoding as a
115 NUL-terminated string, or *NULL*, in which case the default encoding is used.
116 An exception is raised if the named encoding is not known to Python. The
117 second argument must be a :ctype:`char\*\*`; the value of the pointer it
118 references will be set to a buffer with the contents of the argument text.
119 The text will be encoded in the encoding specified by the first argument.
120
121 :cfunc:`PyArg_ParseTuple` will allocate a buffer of the needed size, copy the
122 encoded data into this buffer and adjust *\*buffer* to reference the newly
123 allocated storage. The caller is responsible for calling :cfunc:`PyMem_Free` to
124 free the allocated buffer after use.
125
126``et`` (string, Unicode object or character buffer compatible object) [const char \*encoding, char \*\*buffer]
127 Same as ``es`` except that 8-bit string objects are passed through without
128 recoding them. Instead, the implementation assumes that the string object uses
129 the encoding passed in as parameter.
130
131``es#`` (string, Unicode object or character buffer compatible object) [const char \*encoding, char \*\*buffer, int \*buffer_length]
132 This variant on ``s#`` is used for encoding Unicode and objects convertible to
133 Unicode into a character buffer. Unlike the ``es`` format, this variant allows
134 input data which contains NUL characters.
135
136 It requires three arguments. The first is only used as input, and must be a
137 :ctype:`const char\*` which points to the name of an encoding as a
138 NUL-terminated string, or *NULL*, in which case the default encoding is used.
139 An exception is raised if the named encoding is not known to Python. The
140 second argument must be a :ctype:`char\*\*`; the value of the pointer it
141 references will be set to a buffer with the contents of the argument text.
142 The text will be encoded in the encoding specified by the first argument.
143 The third argument must be a pointer to an integer; the referenced integer
144 will be set to the number of bytes in the output buffer.
145
146 There are two modes of operation:
147
148 If *\*buffer* points a *NULL* pointer, the function will allocate a buffer of
149 the needed size, copy the encoded data into this buffer and set *\*buffer* to
150 reference the newly allocated storage. The caller is responsible for calling
151 :cfunc:`PyMem_Free` to free the allocated buffer after usage.
152
153 If *\*buffer* points to a non-*NULL* pointer (an already allocated buffer),
154 :cfunc:`PyArg_ParseTuple` will use this location as the buffer and interpret the
155 initial value of *\*buffer_length* as the buffer size. It will then copy the
156 encoded data into the buffer and NUL-terminate it. If the buffer is not large
157 enough, a :exc:`ValueError` will be set.
158
159 In both cases, *\*buffer_length* is set to the length of the encoded data
160 without the trailing NUL byte.
161
162``et#`` (string, Unicode object or character buffer compatible object) [const char \*encoding, char \*\*buffer]
163 Same as ``es#`` except that string objects are passed through without recoding
164 them. Instead, the implementation assumes that the string object uses the
165 encoding passed in as parameter.
166
Benjamin Petersonda10d3b2009-01-01 00:23:30 +0000167``b`` (integer) [unsigned char]
168 Convert a nonnegative Python integer to an unsigned tiny int, stored in a C
169 :ctype:`unsigned char`.
Georg Brandl54a3faa2008-01-20 09:30:57 +0000170
171``B`` (integer) [unsigned char]
172 Convert a Python integer to a tiny int without overflow checking, stored in a C
173 :ctype:`unsigned char`.
174
175``h`` (integer) [short int]
176 Convert a Python integer to a C :ctype:`short int`.
177
178``H`` (integer) [unsigned short int]
179 Convert a Python integer to a C :ctype:`unsigned short int`, without overflow
180 checking.
181
182``i`` (integer) [int]
183 Convert a Python integer to a plain C :ctype:`int`.
184
185``I`` (integer) [unsigned int]
186 Convert a Python integer to a C :ctype:`unsigned int`, without overflow
187 checking.
188
189``l`` (integer) [long int]
190 Convert a Python integer to a C :ctype:`long int`.
191
192``k`` (integer) [unsigned long]
193 Convert a Python integer to a C :ctype:`unsigned long` without
194 overflow checking.
195
196``L`` (integer) [PY_LONG_LONG]
197 Convert a Python integer to a C :ctype:`long long`. This format is only
198 available on platforms that support :ctype:`long long` (or :ctype:`_int64` on
199 Windows).
200
201``K`` (integer) [unsigned PY_LONG_LONG]
202 Convert a Python integer to a C :ctype:`unsigned long long`
203 without overflow checking. This format is only available on platforms that
204 support :ctype:`unsigned long long` (or :ctype:`unsigned _int64` on Windows).
205
206``n`` (integer) [Py_ssize_t]
207 Convert a Python integer to a C :ctype:`Py_ssize_t`.
208
209``c`` (string of length 1) [char]
210 Convert a Python character, represented as a string of length 1, to a C
211 :ctype:`char`.
212
213``f`` (float) [float]
214 Convert a Python floating point number to a C :ctype:`float`.
215
216``d`` (float) [double]
217 Convert a Python floating point number to a C :ctype:`double`.
218
219``D`` (complex) [Py_complex]
220 Convert a Python complex number to a C :ctype:`Py_complex` structure.
221
222``O`` (object) [PyObject \*]
223 Store a Python object (without any conversion) in a C object pointer. The C
224 program thus receives the actual object that was passed. The object's reference
225 count is not increased. The pointer stored is not *NULL*.
226
227``O!`` (object) [*typeobject*, PyObject \*]
228 Store a Python object in a C object pointer. This is similar to ``O``, but
229 takes two C arguments: the first is the address of a Python type object, the
230 second is the address of the C variable (of type :ctype:`PyObject\*`) into which
231 the object pointer is stored. If the Python object does not have the required
232 type, :exc:`TypeError` is raised.
233
234``O&`` (object) [*converter*, *anything*]
235 Convert a Python object to a C variable through a *converter* function. This
236 takes two arguments: the first is a function, the second is the address of a C
237 variable (of arbitrary type), converted to :ctype:`void \*`. The *converter*
238 function in turn is called as follows::
239
240 status = converter(object, address);
241
242 where *object* is the Python object to be converted and *address* is the
243 :ctype:`void\*` argument that was passed to the :cfunc:`PyArg_Parse\*` function.
244 The returned *status* should be ``1`` for a successful conversion and ``0`` if
245 the conversion has failed. When the conversion fails, the *converter* function
Christian Heimes78644762008-03-04 23:39:23 +0000246 should raise an exception and leave the content of *address* unmodified.
Georg Brandl54a3faa2008-01-20 09:30:57 +0000247
248``S`` (string) [PyStringObject \*]
249 Like ``O`` but requires that the Python object is a string object. Raises
250 :exc:`TypeError` if the object is not a string object. The C variable may also
251 be declared as :ctype:`PyObject\*`.
252
253``U`` (Unicode string) [PyUnicodeObject \*]
254 Like ``O`` but requires that the Python object is a Unicode object. Raises
255 :exc:`TypeError` if the object is not a Unicode object. The C variable may also
256 be declared as :ctype:`PyObject\*`.
257
258``t#`` (read-only character buffer) [char \*, int]
259 Like ``s#``, but accepts any object which implements the read-only buffer
260 interface. The :ctype:`char\*` variable is set to point to the first byte of
261 the buffer, and the :ctype:`int` is set to the length of the buffer. Only
262 single-segment buffer objects are accepted; :exc:`TypeError` is raised for all
263 others.
264
265``w`` (read-write character buffer) [char \*]
266 Similar to ``s``, but accepts any object which implements the read-write buffer
267 interface. The caller must determine the length of the buffer by other means,
268 or use ``w#`` instead. Only single-segment buffer objects are accepted;
269 :exc:`TypeError` is raised for all others.
270
Georg Brandl8fa89522008-09-01 16:45:35 +0000271``w*`` (read-write byte-oriented buffer) [Py_buffer \*]
272 This is to ``w`` what ``s*`` is to ``s``.
273
Georg Brandl54a3faa2008-01-20 09:30:57 +0000274``w#`` (read-write character buffer) [char \*, int]
275 Like ``s#``, but accepts any object which implements the read-write buffer
276 interface. The :ctype:`char \*` variable is set to point to the first byte of
277 the buffer, and the :ctype:`int` is set to the length of the buffer. Only
278 single-segment buffer objects are accepted; :exc:`TypeError` is raised for all
279 others.
280
281``(items)`` (tuple) [*matching-items*]
282 The object must be a Python sequence whose length is the number of format units
283 in *items*. The C arguments must correspond to the individual format units in
284 *items*. Format units for sequences may be nested.
285
286It is possible to pass "long" integers (integers whose value exceeds the
287platform's :const:`LONG_MAX`) however no proper range checking is done --- the
288most significant bits are silently truncated when the receiving field is too
289small to receive the value (actually, the semantics are inherited from downcasts
290in C --- your mileage may vary).
291
292A few other characters have a meaning in a format string. These may not occur
293inside nested parentheses. They are:
294
295``|``
296 Indicates that the remaining arguments in the Python argument list are optional.
297 The C variables corresponding to optional arguments should be initialized to
298 their default value --- when an optional argument is not specified,
299 :cfunc:`PyArg_ParseTuple` does not touch the contents of the corresponding C
300 variable(s).
301
302``:``
303 The list of format units ends here; the string after the colon is used as the
304 function name in error messages (the "associated value" of the exception that
305 :cfunc:`PyArg_ParseTuple` raises).
306
307``;``
308 The list of format units ends here; the string after the semicolon is used as
Benjamin Peterson92035012008-12-27 16:00:54 +0000309 the error message *instead* of the default error message. ``:`` and ``;``
310 mutually exclude each other.
Georg Brandl54a3faa2008-01-20 09:30:57 +0000311
312Note that any Python object references which are provided to the caller are
313*borrowed* references; do not decrement their reference count!
314
315Additional arguments passed to these functions must be addresses of variables
316whose type is determined by the format string; these are used to store values
317from the input tuple. There are a few cases, as described in the list of format
318units above, where these parameters are used as input values; they should match
319what is specified for the corresponding format unit in that case.
320
Christian Heimes78644762008-03-04 23:39:23 +0000321For the conversion to succeed, the *arg* object must match the format
322and the format must be exhausted. On success, the
323:cfunc:`PyArg_Parse\*` functions return true, otherwise they return
324false and raise an appropriate exception. When the
325:cfunc:`PyArg_Parse\*` functions fail due to conversion failure in one
326of the format units, the variables at the addresses corresponding to that
327and the following format units are left untouched.
Georg Brandl54a3faa2008-01-20 09:30:57 +0000328
329
330.. cfunction:: int PyArg_ParseTuple(PyObject *args, const char *format, ...)
331
332 Parse the parameters of a function that takes only positional parameters into
333 local variables. Returns true on success; on failure, it returns false and
334 raises the appropriate exception.
335
336
337.. cfunction:: int PyArg_VaParse(PyObject *args, const char *format, va_list vargs)
338
339 Identical to :cfunc:`PyArg_ParseTuple`, except that it accepts a va_list rather
340 than a variable number of arguments.
341
342
343.. cfunction:: int PyArg_ParseTupleAndKeywords(PyObject *args, PyObject *kw, const char *format, char *keywords[], ...)
344
345 Parse the parameters of a function that takes both positional and keyword
346 parameters into local variables. Returns true on success; on failure, it
347 returns false and raises the appropriate exception.
348
349
350.. cfunction:: int PyArg_VaParseTupleAndKeywords(PyObject *args, PyObject *kw, const char *format, char *keywords[], va_list vargs)
351
352 Identical to :cfunc:`PyArg_ParseTupleAndKeywords`, except that it accepts a
353 va_list rather than a variable number of arguments.
354
355
356.. XXX deprecated, will be removed
357.. cfunction:: int PyArg_Parse(PyObject *args, const char *format, ...)
358
359 Function used to deconstruct the argument lists of "old-style" functions ---
360 these are functions which use the :const:`METH_OLDARGS` parameter parsing
361 method. This is not recommended for use in parameter parsing in new code, and
362 most code in the standard interpreter has been modified to no longer use this
363 for that purpose. It does remain a convenient way to decompose other tuples,
364 however, and may continue to be used for that purpose.
365
366
367.. cfunction:: int PyArg_UnpackTuple(PyObject *args, const char *name, Py_ssize_t min, Py_ssize_t max, ...)
368
369 A simpler form of parameter retrieval which does not use a format string to
370 specify the types of the arguments. Functions which use this method to retrieve
371 their parameters should be declared as :const:`METH_VARARGS` in function or
372 method tables. The tuple containing the actual parameters should be passed as
373 *args*; it must actually be a tuple. The length of the tuple must be at least
374 *min* and no more than *max*; *min* and *max* may be equal. Additional
375 arguments must be passed to the function, each of which should be a pointer to a
376 :ctype:`PyObject\*` variable; these will be filled in with the values from
377 *args*; they will contain borrowed references. The variables which correspond
378 to optional parameters not given by *args* will not be filled in; these should
379 be initialized by the caller. This function returns true on success and false if
380 *args* is not a tuple or contains the wrong number of elements; an exception
381 will be set if there was a failure.
382
383 This is an example of the use of this function, taken from the sources for the
384 :mod:`_weakref` helper module for weak references::
385
386 static PyObject *
387 weakref_ref(PyObject *self, PyObject *args)
388 {
389 PyObject *object;
390 PyObject *callback = NULL;
391 PyObject *result = NULL;
392
393 if (PyArg_UnpackTuple(args, "ref", 1, 2, &object, &callback)) {
394 result = PyWeakref_NewRef(object, callback);
395 }
396 return result;
397 }
398
399 The call to :cfunc:`PyArg_UnpackTuple` in this example is entirely equivalent to
400 this call to :cfunc:`PyArg_ParseTuple`::
401
402 PyArg_ParseTuple(args, "O|O:ref", &object, &callback)
403
404
405.. cfunction:: PyObject* Py_BuildValue(const char *format, ...)
406
407 Create a new value based on a format string similar to those accepted by the
408 :cfunc:`PyArg_Parse\*` family of functions and a sequence of values. Returns
409 the value or *NULL* in the case of an error; an exception will be raised if
410 *NULL* is returned.
411
412 :cfunc:`Py_BuildValue` does not always build a tuple. It builds a tuple only if
413 its format string contains two or more format units. If the format string is
414 empty, it returns ``None``; if it contains exactly one format unit, it returns
415 whatever object is described by that format unit. To force it to return a tuple
416 of size 0 or one, parenthesize the format string.
417
418 When memory buffers are passed as parameters to supply data to build objects, as
419 for the ``s`` and ``s#`` formats, the required data is copied. Buffers provided
420 by the caller are never referenced by the objects created by
421 :cfunc:`Py_BuildValue`. In other words, if your code invokes :cfunc:`malloc`
422 and passes the allocated memory to :cfunc:`Py_BuildValue`, your code is
423 responsible for calling :cfunc:`free` for that memory once
424 :cfunc:`Py_BuildValue` returns.
425
426 In the following description, the quoted form is the format unit; the entry in
427 (round) parentheses is the Python object type that the format unit will return;
428 and the entry in [square] brackets is the type of the C value(s) to be passed.
429
430 The characters space, tab, colon and comma are ignored in format strings (but
431 not within format units such as ``s#``). This can be used to make long format
432 strings a tad more readable.
433
434 ``s`` (string) [char \*]
435 Convert a null-terminated C string to a Python object. If the C string pointer
436 is *NULL*, ``None`` is used.
437
438 ``s#`` (string) [char \*, int]
439 Convert a C string and its length to a Python object. If the C string pointer
440 is *NULL*, the length is ignored and ``None`` is returned.
441
Georg Brandl7a259ca2008-12-05 07:57:51 +0000442 ``y`` (bytes) [char \*]
Benjamin Petersonffc94792008-10-21 21:10:07 +0000443 This converts a C string to a Python :func:`bytes` object. If the C
444 string pointer is *NULL*, ``None`` is returned.
445
446 ``y#`` (bytes) [char \*, int]
447 This converts a C string and its lengths to a Python object. If the C
448 string pointer is *NULL*, ``None`` is returned.
449
Georg Brandl54a3faa2008-01-20 09:30:57 +0000450 ``z`` (string or ``None``) [char \*]
451 Same as ``s``.
452
453 ``z#`` (string or ``None``) [char \*, int]
454 Same as ``s#``.
455
456 ``u`` (Unicode string) [Py_UNICODE \*]
457 Convert a null-terminated buffer of Unicode (UCS-2 or UCS-4) data to a Python
458 Unicode object. If the Unicode buffer pointer is *NULL*, ``None`` is returned.
459
460 ``u#`` (Unicode string) [Py_UNICODE \*, int]
461 Convert a Unicode (UCS-2 or UCS-4) data buffer and its length to a Python
462 Unicode object. If the Unicode buffer pointer is *NULL*, the length is ignored
463 and ``None`` is returned.
464
465 ``U`` (string) [char \*]
466 Convert a null-terminated C string to a Python unicode object. If the C string
467 pointer is *NULL*, ``None`` is used.
468
469 ``U#`` (string) [char \*, int]
470 Convert a C string and its length to a Python unicode object. If the C string
471 pointer is *NULL*, the length is ignored and ``None`` is returned.
472
473 ``i`` (integer) [int]
474 Convert a plain C :ctype:`int` to a Python integer object.
475
476 ``b`` (integer) [char]
477 Convert a plain C :ctype:`char` to a Python integer object.
478
479 ``h`` (integer) [short int]
480 Convert a plain C :ctype:`short int` to a Python integer object.
481
482 ``l`` (integer) [long int]
483 Convert a C :ctype:`long int` to a Python integer object.
484
485 ``B`` (integer) [unsigned char]
486 Convert a C :ctype:`unsigned char` to a Python integer object.
487
488 ``H`` (integer) [unsigned short int]
489 Convert a C :ctype:`unsigned short int` to a Python integer object.
490
491 ``I`` (integer/long) [unsigned int]
492 Convert a C :ctype:`unsigned int` to a Python long integer object.
493
494 ``k`` (integer/long) [unsigned long]
495 Convert a C :ctype:`unsigned long` to a Python long integer object.
496
497 ``L`` (long) [PY_LONG_LONG]
498 Convert a C :ctype:`long long` to a Python integer object. Only available
499 on platforms that support :ctype:`long long`.
500
501 ``K`` (long) [unsigned PY_LONG_LONG]
502 Convert a C :ctype:`unsigned long long` to a Python integer object. Only
503 available on platforms that support :ctype:`unsigned long long`.
504
505 ``n`` (int) [Py_ssize_t]
506 Convert a C :ctype:`Py_ssize_t` to a Python integer.
507
508 ``c`` (string of length 1) [char]
509 Convert a C :ctype:`int` representing a character to a Python string of length
510 1.
511
512 ``d`` (float) [double]
513 Convert a C :ctype:`double` to a Python floating point number.
514
515 ``f`` (float) [float]
516 Same as ``d``.
517
518 ``D`` (complex) [Py_complex \*]
519 Convert a C :ctype:`Py_complex` structure to a Python complex number.
520
521 ``O`` (object) [PyObject \*]
522 Pass a Python object untouched (except for its reference count, which is
523 incremented by one). If the object passed in is a *NULL* pointer, it is assumed
524 that this was caused because the call producing the argument found an error and
525 set an exception. Therefore, :cfunc:`Py_BuildValue` will return *NULL* but won't
526 raise an exception. If no exception has been raised yet, :exc:`SystemError` is
527 set.
528
529 ``S`` (object) [PyObject \*]
530 Same as ``O``.
531
532 ``N`` (object) [PyObject \*]
533 Same as ``O``, except it doesn't increment the reference count on the object.
534 Useful when the object is created by a call to an object constructor in the
535 argument list.
536
537 ``O&`` (object) [*converter*, *anything*]
538 Convert *anything* to a Python object through a *converter* function. The
539 function is called with *anything* (which should be compatible with :ctype:`void
540 \*`) as its argument and should return a "new" Python object, or *NULL* if an
541 error occurred.
542
543 ``(items)`` (tuple) [*matching-items*]
544 Convert a sequence of C values to a Python tuple with the same number of items.
545
546 ``[items]`` (list) [*matching-items*]
547 Convert a sequence of C values to a Python list with the same number of items.
548
549 ``{items}`` (dictionary) [*matching-items*]
550 Convert a sequence of C values to a Python dictionary. Each pair of consecutive
551 C values adds one item to the dictionary, serving as key and value,
552 respectively.
553
554 If there is an error in the format string, the :exc:`SystemError` exception is
555 set and *NULL* returned.
Benjamin Petersonda10d3b2009-01-01 00:23:30 +0000556
557.. cfunction:: PyObject* Py_VaBuildValue(const char *format, va_list vargs)
558
559 Identical to :cfunc:`Py_BuildValue`, except that it accepts a va_list
560 rather than a variable number of arguments.