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