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