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