source: python/trunk/Doc/c-api/arg.rst

Last change on this file was 391, checked in by dmik, 11 years ago

python: Merge vendor 2.7.6 to trunk.

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