7 The Python interpreter has a number of functions built into it that are always
8 available. They are listed here in alphabetical order.
11 .. function:: __import__(name[, globals[, locals[, fromlist[, level]]]])
21 This is an advanced function that is not needed in everyday Python
24 The function is invoked by the :keyword:`import` statement. It mainly exists
25 so that you can replace it with another function that has a compatible
26 interface, in order to change the semantics of the :keyword:`import` statement.
27 For examples of why and how you would do this, see the standard library modules
28 :mod:`ihooks` and :mod:`rexec`. See also the built-in module :mod:`imp`, which
29 defines some useful operations out of which you can build your own
30 :func:`__import__` function.
32 For example, the statement ``import spam`` results in the following call:
33 ``__import__('spam', globals(), locals(), [], -1)``; the statement
34 ``from spam.ham import eggs`` results in ``__import__('spam.ham', globals(),
35 locals(), ['eggs'], -1)``. Note that even though ``locals()`` and ``['eggs']``
36 are passed in as arguments, the :func:`__import__` function does not set the
37 local variable named ``eggs``; this is done by subsequent code that is generated
38 for the import statement. (In fact, the standard implementation does not use
39 its *locals* argument at all, and uses its *globals* only to determine the
40 package context of the :keyword:`import` statement.)
42 When the *name* variable is of the form ``package.module``, normally, the
43 top-level package (the name up till the first dot) is returned, *not* the
44 module named by *name*. However, when a non-empty *fromlist* argument is
45 given, the module named by *name* is returned. This is done for
46 compatibility with the :term:`bytecode` generated for the different kinds of import
47 statement; when using ``import spam.ham.eggs``, the top-level package
48 :mod:`spam` must be placed in the importing namespace, but when using ``from
49 spam.ham import eggs``, the ``spam.ham`` subpackage must be used to find the
50 ``eggs`` variable. As a workaround for this behavior, use :func:`getattr` to
51 extract the desired components. For example, you could define the following
55 mod = __import__(name)
56 components = name.split('.')
57 for comp in components[1:]:
58 mod = getattr(mod, comp)
61 *level* specifies whether to use absolute or relative imports. The default is
62 ``-1`` which indicates both absolute and relative imports will be attempted.
63 ``0`` means only perform absolute imports. Positive values for *level* indicate
64 the number of parent directories to search relative to the directory of the
65 module calling :func:`__import__`.
67 .. versionchanged:: 2.5
68 The level parameter was added.
70 .. versionchanged:: 2.5
71 Keyword support for parameters was added.
76 Return the absolute value of a number. The argument may be a plain or long
77 integer or a floating point number. If the argument is a complex number, its
78 magnitude is returned.
81 .. function:: all(iterable)
83 Return True if all elements of the *iterable* are true. Equivalent to::
86 for element in iterable:
94 .. function:: any(iterable)
96 Return True if any element of the *iterable* is true. Equivalent to::
99 for element in iterable:
104 .. versionadded:: 2.5
107 .. function:: basestring()
109 This abstract type is the superclass for :class:`str` and :class:`unicode`. It
110 cannot be called or instantiated, but it can be used to test whether an object
111 is an instance of :class:`str` or :class:`unicode`. ``isinstance(obj,
112 basestring)`` is equivalent to ``isinstance(obj, (str, unicode))``.
114 .. versionadded:: 2.3
117 .. function:: bool([x])
119 Convert a value to a Boolean, using the standard truth testing procedure. If
120 *x* is false or omitted, this returns :const:`False`; otherwise it returns
121 :const:`True`. :class:`bool` is also a class, which is a subclass of
122 :class:`int`. Class :class:`bool` cannot be subclassed further. Its only
123 instances are :const:`False` and :const:`True`.
125 .. index:: pair: Boolean; type
127 .. versionadded:: 2.2.1
129 .. versionchanged:: 2.3
130 If no argument is given, this function returns :const:`False`.
133 .. function:: callable(object)
135 Return :const:`True` if the *object* argument appears callable,
136 :const:`False` if not. If this
137 returns true, it is still possible that a call fails, but if it is false,
138 calling *object* will never succeed. Note that classes are callable (calling a
139 class returns a new instance); class instances are callable if they have a
140 :meth:`__call__` method.
145 Return a string of one character whose ASCII code is the integer *i*. For
146 example, ``chr(97)`` returns the string ``'a'``. This is the inverse of
147 :func:`ord`. The argument must be in the range [0..255], inclusive;
148 :exc:`ValueError` will be raised if *i* is outside that range. See
152 .. function:: classmethod(function)
154 Return a class method for *function*.
156 A class method receives the class as implicit first argument, just like an
157 instance method receives the instance. To declare a class method, use this
162 def f(cls, arg1, arg2, ...): ...
164 The ``@classmethod`` form is a function :term:`decorator` -- see the description
165 of function definitions in :ref:`function` for details.
167 It can be called either on the class (such as ``C.f()``) or on an instance (such
168 as ``C().f()``). The instance is ignored except for its class. If a class
169 method is called for a derived class, the derived class object is passed as the
170 implied first argument.
172 Class methods are different than C++ or Java static methods. If you want those,
173 see :func:`staticmethod` in this section.
175 For more information on class methods, consult the documentation on the standard
176 type hierarchy in :ref:`types`.
178 .. versionadded:: 2.2
180 .. versionchanged:: 2.4
181 Function decorator syntax added.
184 .. function:: cmp(x, y)
186 Compare the two objects *x* and *y* and return an integer according to the
187 outcome. The return value is negative if ``x < y``, zero if ``x == y`` and
188 strictly positive if ``x > y``.
191 .. function:: compile(source, filename, mode[, flags[, dont_inherit]])
193 Compile the *source* into a code object. Code objects can be executed by an
194 :keyword:`exec` statement or evaluated by a call to :func:`eval`. The
195 *filename* argument should give the file from which the code was read; pass some
196 recognizable value if it wasn't read from a file (``'<string>'`` is commonly
197 used). The *mode* argument specifies what kind of code must be compiled; it can
198 be ``'exec'`` if *source* consists of a sequence of statements, ``'eval'`` if it
199 consists of a single expression, or ``'single'`` if it consists of a single
200 interactive statement (in the latter case, expression statements that evaluate
201 to something else than ``None`` will be printed).
203 When compiling multi-line statements, two caveats apply: line endings must be
204 represented by a single newline character (``'\n'``), and the input must be
205 terminated by at least one newline character. If line endings are represented
206 by ``'\r\n'``, use the string :meth:`replace` method to change them into
209 The optional arguments *flags* and *dont_inherit* (which are new in Python 2.2)
210 control which future statements (see :pep:`236`) affect the compilation of
211 *source*. If neither is present (or both are zero) the code is compiled with
212 those future statements that are in effect in the code that is calling compile.
213 If the *flags* argument is given and *dont_inherit* is not (or is zero) then the
214 future statements specified by the *flags* argument are used in addition to
215 those that would be used anyway. If *dont_inherit* is a non-zero integer then
216 the *flags* argument is it -- the future statements in effect around the call to
219 Future statements are specified by bits which can be bitwise ORed together to
220 specify multiple statements. The bitfield required to specify a given feature
221 can be found as the :attr:`compiler_flag` attribute on the :class:`_Feature`
222 instance in the :mod:`__future__` module.
224 This function raises :exc:`SyntaxError` if the compiled source is invalid,
225 and :exc:`TypeError` if the source contains null bytes.
228 .. function:: complex([real[, imag]])
230 Create a complex number with the value *real* + *imag*\*j or convert a string or
231 number to a complex number. If the first parameter is a string, it will be
232 interpreted as a complex number and the function must be called without a second
233 parameter. The second parameter can never be a string. Each argument may be any
234 numeric type (including complex). If *imag* is omitted, it defaults to zero and
235 the function serves as a numeric conversion function like :func:`int`,
236 :func:`long` and :func:`float`. If both arguments are omitted, returns ``0j``.
238 The complex type is described in :ref:`typesnumeric`.
241 .. function:: delattr(object, name)
243 This is a relative of :func:`setattr`. The arguments are an object and a
244 string. The string must be the name of one of the object's attributes. The
245 function deletes the named attribute, provided the object allows it. For
246 example, ``delattr(x, 'foobar')`` is equivalent to ``del x.foobar``.
249 .. function:: dict([arg])
252 Create a new data dictionary, optionally with items taken from *arg*.
253 The dictionary type is described in :ref:`typesmapping`.
255 For other containers see the built in :class:`list`, :class:`set`, and
256 :class:`tuple` classes, and the :mod:`collections` module.
259 .. function:: dir([object])
261 Without arguments, return the list of names in the current local scope. With an
262 argument, attempt to return a list of valid attributes for that object.
264 If the object has a method named :meth:`__dir__`, this method will be called and
265 must return the list of attributes. This allows objects that implement a custom
266 :func:`__getattr__` or :func:`__getattribute__` function to customize the way
267 :func:`dir` reports their attributes.
269 If the object does not provide :meth:`__dir__`, the function tries its best to
270 gather information from the object's :attr:`__dict__` attribute, if defined, and
271 from its type object. The resulting list is not necessarily complete, and may
272 be inaccurate when the object has a custom :func:`__getattr__`.
274 The default :func:`dir` mechanism behaves differently with different types of
275 objects, as it attempts to produce the most relevant, rather than complete,
278 * If the object is a module object, the list contains the names of the module's
281 * If the object is a type or class object, the list contains the names of its
282 attributes, and recursively of the attributes of its bases.
284 * Otherwise, the list contains the object's attributes' names, the names of its
285 class's attributes, and recursively of the attributes of its class's base
288 The resulting list is sorted alphabetically. For example::
292 ['__builtins__', '__doc__', '__name__', 'struct']
294 ['__doc__', '__name__', 'calcsize', 'error', 'pack', 'unpack']
295 >>> class Foo(object):
296 ... def __dir__(self):
297 ... return ["kan", "ga", "roo"]
305 Because :func:`dir` is supplied primarily as a convenience for use at an
306 interactive prompt, it tries to supply an interesting set of names more than it
307 tries to supply a rigorously or consistently defined set of names, and its
308 detailed behavior may change across releases. For example, metaclass attributes
309 are not in the result list when the argument is a class.
312 .. function:: divmod(a, b)
314 Take two (non complex) numbers as arguments and return a pair of numbers
315 consisting of their quotient and remainder when using long division. With mixed
316 operand types, the rules for binary arithmetic operators apply. For plain and
317 long integers, the result is the same as ``(a // b, a % b)``. For floating point
318 numbers the result is ``(q, a % b)``, where *q* is usually ``math.floor(a / b)``
319 but may be 1 less than that. In any case ``q * b + a % b`` is very close to
320 *a*, if ``a % b`` is non-zero it has the same sign as *b*, and ``0 <= abs(a % b)
323 .. versionchanged:: 2.3
324 Using :func:`divmod` with complex numbers is deprecated.
327 .. function:: enumerate(iterable)
329 Return an enumerate object. *iterable* must be a sequence, an :term:`iterator`, or some
330 other object which supports iteration. The :meth:`next` method of the iterator
331 returned by :func:`enumerate` returns a tuple containing a count (from zero) and
332 the corresponding value obtained from iterating over *iterable*.
333 :func:`enumerate` is useful for obtaining an indexed series: ``(0, seq[0])``,
334 ``(1, seq[1])``, ``(2, seq[2])``, .... For example::
336 >>> for i, season in enumerate(['Spring', 'Summer', 'Fall', 'Winter')]:
343 .. versionadded:: 2.3
346 .. function:: eval(expression[, globals[, locals]])
348 The arguments are a string and optional globals and locals. If provided,
349 *globals* must be a dictionary. If provided, *locals* can be any mapping
352 .. versionchanged:: 2.4
353 formerly *locals* was required to be a dictionary.
355 The *expression* argument is parsed and evaluated as a Python expression
356 (technically speaking, a condition list) using the *globals* and *locals*
357 dictionaries as global and local namespace. If the *globals* dictionary is
358 present and lacks '__builtins__', the current globals are copied into *globals*
359 before *expression* is parsed. This means that *expression* normally has full
360 access to the standard :mod:`__builtin__` module and restricted environments are
361 propagated. If the *locals* dictionary is omitted it defaults to the *globals*
362 dictionary. If both dictionaries are omitted, the expression is executed in the
363 environment where :func:`eval` is called. The return value is the result of
364 the evaluated expression. Syntax errors are reported as exceptions. Example::
367 >>> print eval('x+1')
370 This function can also be used to execute arbitrary code objects (such as those
371 created by :func:`compile`). In this case pass a code object instead of a
372 string. The code object must have been compiled passing ``'eval'`` as the
375 Hints: dynamic execution of statements is supported by the :keyword:`exec`
376 statement. Execution of statements from a file is supported by the
377 :func:`execfile` function. The :func:`globals` and :func:`locals` functions
378 returns the current global and local dictionary, respectively, which may be
379 useful to pass around for use by :func:`eval` or :func:`execfile`.
382 .. function:: execfile(filename[, globals[, locals]])
384 This function is similar to the :keyword:`exec` statement, but parses a file
385 instead of a string. It is different from the :keyword:`import` statement in
386 that it does not use the module administration --- it reads the file
387 unconditionally and does not create a new module. [#]_
389 The arguments are a file name and two optional dictionaries. The file is parsed
390 and evaluated as a sequence of Python statements (similarly to a module) using
391 the *globals* and *locals* dictionaries as global and local namespace. If
392 provided, *locals* can be any mapping object.
394 .. versionchanged:: 2.4
395 formerly *locals* was required to be a dictionary.
397 If the *locals* dictionary is omitted it defaults to the *globals* dictionary.
398 If both dictionaries are omitted, the expression is executed in the environment
399 where :func:`execfile` is called. The return value is ``None``.
403 The default *locals* act as described for function :func:`locals` below:
404 modifications to the default *locals* dictionary should not be attempted. Pass
405 an explicit *locals* dictionary if you need to see effects of the code on
406 *locals* after function :func:`execfile` returns. :func:`execfile` cannot be
407 used reliably to modify a function's locals.
410 .. function:: file(filename[, mode[, bufsize]])
412 Constructor function for the :class:`file` type, described further in section
413 :ref:`bltin-file-objects`. The constructor's arguments are the same as those
414 of the :func:`open` built-in function described below.
416 When opening a file, it's preferable to use :func:`open` instead of invoking
417 this constructor directly. :class:`file` is more suited to type testing (for
418 example, writing ``isinstance(f, file)``).
420 .. versionadded:: 2.2
423 .. function:: filter(function, iterable)
425 Construct a list from those elements of *iterable* for which *function* returns
426 true. *iterable* may be either a sequence, a container which supports
427 iteration, or an iterator. If *iterable* is a string or a tuple, the result
428 also has that type; otherwise it is always a list. If *function* is ``None``,
429 the identity function is assumed, that is, all elements of *iterable* that are
432 Note that ``filter(function, iterable)`` is equivalent to ``[item for item in
433 iterable if function(item)]`` if function is not ``None`` and ``[item for item
434 in iterable if item]`` if function is ``None``.
437 .. function:: float([x])
439 Convert a string or a number to floating point. If the argument is a string, it
440 must contain a possibly signed decimal or floating point number, possibly
441 embedded in whitespace. The argument may also be [+|-]nan or [+|-]inf.
442 Otherwise, the argument may be a plain or long integer
443 or a floating point number, and a floating point number with the same value
444 (within Python's floating point precision) is returned. If no argument is
445 given, returns ``0.0``.
453 When passing in a string, values for NaN and Infinity may be returned, depending
454 on the underlying C library. Float accepts the strings nan, inf and -inf for
455 NaN and positive or negative infinity. The case and a leading + are ignored as
456 well as a leading - is ignored for NaN. Float always represents NaN and infinity
459 The float type is described in :ref:`typesnumeric`.
461 .. function:: frozenset([iterable])
464 Return a frozenset object, optionally with elements taken from *iterable*.
465 The frozenset type is described in :ref:`types-set`.
467 For other containers see the built in :class:`dict`, :class:`list`, and
468 :class:`tuple` classes, and the :mod:`collections` module.
470 .. versionadded:: 2.4
473 .. function:: getattr(object, name[, default])
475 Return the value of the named attributed of *object*. *name* must be a string.
476 If the string is the name of one of the object's attributes, the result is the
477 value of that attribute. For example, ``getattr(x, 'foobar')`` is equivalent to
478 ``x.foobar``. If the named attribute does not exist, *default* is returned if
479 provided, otherwise :exc:`AttributeError` is raised.
482 .. function:: globals()
484 Return a dictionary representing the current global symbol table. This is always
485 the dictionary of the current module (inside a function or method, this is the
486 module where it is defined, not the module from which it is called).
489 .. function:: hasattr(object, name)
491 The arguments are an object and a string. The result is ``True`` if the string
492 is the name of one of the object's attributes, ``False`` if not. (This is
493 implemented by calling ``getattr(object, name)`` and seeing whether it raises an
497 .. function:: hash(object)
499 Return the hash value of the object (if it has one). Hash values are integers.
500 They are used to quickly compare dictionary keys during a dictionary lookup.
501 Numeric values that compare equal have the same hash value (even if they are of
502 different types, as is the case for 1 and 1.0).
505 .. function:: help([object])
507 Invoke the built-in help system. (This function is intended for interactive
508 use.) If no argument is given, the interactive help system starts on the
509 interpreter console. If the argument is a string, then the string is looked up
510 as the name of a module, function, class, method, keyword, or documentation
511 topic, and a help page is printed on the console. If the argument is any other
512 kind of object, a help page on the object is generated.
514 .. versionadded:: 2.2
519 Convert an integer number (of any size) to a hexadecimal string. The result is a
520 valid Python expression.
522 .. versionchanged:: 2.4
523 Formerly only returned an unsigned literal.
526 .. function:: id(object)
528 Return the "identity" of an object. This is an integer (or long integer) which
529 is guaranteed to be unique and constant for this object during its lifetime.
530 Two objects with non-overlapping lifetimes may have the same :func:`id` value.
531 (Implementation note: this is the address of the object.)
534 .. function:: input([prompt])
536 Equivalent to ``eval(raw_input(prompt))``.
540 This function is not safe from user errors! It expects a valid Python
541 expression as input; if the input is not syntactically valid, a
542 :exc:`SyntaxError` will be raised. Other exceptions may be raised if there is an
543 error during evaluation. (On the other hand, sometimes this is exactly what you
544 need when writing a quick script for expert use.)
546 If the :mod:`readline` module was loaded, then :func:`input` will use it to
547 provide elaborate line editing and history features.
549 Consider using the :func:`raw_input` function for general input from users.
552 .. function:: int([x[, radix]])
554 Convert a string or number to a plain integer. If the argument is a string,
555 it must contain a possibly signed decimal number representable as a Python
556 integer, possibly embedded in whitespace. The *radix* parameter gives the
557 base for the conversion (which is 10 by default) and may be any integer in
558 the range [2, 36], or zero. If *radix* is zero, the proper radix is guessed
559 based on the contents of string; the interpretation is the same as for
560 integer literals. If *radix* is specified and *x* is not a string,
561 :exc:`TypeError` is raised. Otherwise, the argument may be a plain or long
562 integer or a floating point number. Conversion of floating point numbers to
563 integers truncates (towards zero). If the argument is outside the integer
564 range a long object will be returned instead. If no arguments are given,
567 The integer type is described in :ref:`typesnumeric`.
570 .. function:: isinstance(object, classinfo)
572 Return true if the *object* argument is an instance of the *classinfo* argument,
573 or of a (direct or indirect) subclass thereof. Also return true if *classinfo*
574 is a type object (new-style class) and *object* is an object of that type or of
575 a (direct or indirect) subclass thereof. If *object* is not a class instance or
576 an object of the given type, the function always returns false. If *classinfo*
577 is neither a class object nor a type object, it may be a tuple of class or type
578 objects, or may recursively contain other such tuples (other sequence types are
579 not accepted). If *classinfo* is not a class, type, or tuple of classes, types,
580 and such tuples, a :exc:`TypeError` exception is raised.
582 .. versionchanged:: 2.2
583 Support for a tuple of type information was added.
586 .. function:: issubclass(class, classinfo)
588 Return true if *class* is a subclass (direct or indirect) of *classinfo*. A
589 class is considered a subclass of itself. *classinfo* may be a tuple of class
590 objects, in which case every entry in *classinfo* will be checked. In any other
591 case, a :exc:`TypeError` exception is raised.
593 .. versionchanged:: 2.3
594 Support for a tuple of type information was added.
597 .. function:: iter(o[, sentinel])
599 Return an :term:`iterator` object. The first argument is interpreted very differently
600 depending on the presence of the second argument. Without a second argument, *o*
601 must be a collection object which supports the iteration protocol (the
602 :meth:`__iter__` method), or it must support the sequence protocol (the
603 :meth:`__getitem__` method with integer arguments starting at ``0``). If it
604 does not support either of those protocols, :exc:`TypeError` is raised. If the
605 second argument, *sentinel*, is given, then *o* must be a callable object. The
606 iterator created in this case will call *o* with no arguments for each call to
607 its :meth:`next` method; if the value returned is equal to *sentinel*,
608 :exc:`StopIteration` will be raised, otherwise the value will be returned.
610 .. versionadded:: 2.2
615 Return the length (the number of items) of an object. The argument may be a
616 sequence (string, tuple or list) or a mapping (dictionary).
619 .. function:: list([iterable])
621 Return a list whose items are the same and in the same order as *iterable*'s
622 items. *iterable* may be either a sequence, a container that supports
623 iteration, or an iterator object. If *iterable* is already a list, a copy is
624 made and returned, similar to ``iterable[:]``. For instance, ``list('abc')``
625 returns ``['a', 'b', 'c']`` and ``list( (1, 2, 3) )`` returns ``[1, 2, 3]``. If
626 no argument is given, returns a new empty list, ``[]``.
628 :class:`list` is a mutable sequence type, as documented in
629 :ref:`typesseq`. For other containers see the built in :class:`dict`,
630 :class:`set`, and :class:`tuple` classes, and the :mod:`collections` module.
633 .. function:: locals()
635 Update and return a dictionary representing the current local symbol table.
639 The contents of this dictionary should not be modified; changes may not affect
640 the values of local variables used by the interpreter.
642 Free variables are returned by :func:`locals` when it is called in a function block.
643 Modifications of free variables may not affect the values used by the
644 interpreter. Free variables are not returned in class blocks.
647 .. function:: long([x[, radix]])
649 Convert a string or number to a long integer. If the argument is a string, it
650 must contain a possibly signed number of arbitrary size, possibly embedded in
651 whitespace. The *radix* argument is interpreted in the same way as for
652 :func:`int`, and may only be given when *x* is a string. Otherwise, the argument
653 may be a plain or long integer or a floating point number, and a long integer
654 with the same value is returned. Conversion of floating point numbers to
655 integers truncates (towards zero). If no arguments are given, returns ``0L``.
657 The long type is described in :ref:`typesnumeric`.
659 .. function:: map(function, iterable, ...)
661 Apply *function* to every item of *iterable* and return a list of the results.
662 If additional *iterable* arguments are passed, *function* must take that many
663 arguments and is applied to the items from all iterables in parallel. If one
664 iterable is shorter than another it is assumed to be extended with ``None``
665 items. If *function* is ``None``, the identity function is assumed; if there
666 are multiple arguments, :func:`map` returns a list consisting of tuples
667 containing the corresponding items from all iterables (a kind of transpose
668 operation). The *iterable* arguments may be a sequence or any iterable object;
669 the result is always a list.
672 .. function:: max(iterable[, args...][key])
674 With a single argument *iterable*, return the largest item of a non-empty
675 iterable (such as a string, tuple or list). With more than one argument, return
676 the largest of the arguments.
678 The optional *key* argument specifies a one-argument ordering function like that
679 used for :meth:`list.sort`. The *key* argument, if supplied, must be in keyword
680 form (for example, ``max(a,b,c,key=func)``).
682 .. versionchanged:: 2.5
683 Added support for the optional *key* argument.
686 .. function:: min(iterable[, args...][key])
688 With a single argument *iterable*, return the smallest item of a non-empty
689 iterable (such as a string, tuple or list). With more than one argument, return
690 the smallest of the arguments.
692 The optional *key* argument specifies a one-argument ordering function like that
693 used for :meth:`list.sort`. The *key* argument, if supplied, must be in keyword
694 form (for example, ``min(a,b,c,key=func)``).
696 .. versionchanged:: 2.5
697 Added support for the optional *key* argument.
700 .. function:: object()
702 Return a new featureless object. :class:`object` is a base for all new style
703 classes. It has the methods that are common to all instances of new style
706 .. versionadded:: 2.2
708 .. versionchanged:: 2.3
709 This function does not accept any arguments. Formerly, it accepted arguments but
715 Convert an integer number (of any size) to an octal string. The result is a
716 valid Python expression.
718 .. versionchanged:: 2.4
719 Formerly only returned an unsigned literal.
722 .. function:: open(filename[, mode[, bufsize]])
724 Open a file, returning an object of the :class:`file` type described in
725 section :ref:`bltin-file-objects`. If the file cannot be opened,
726 :exc:`IOError` is raised. When opening a file, it's preferable to use
727 :func:`open` instead of invoking the :class:`file` constructor directly.
729 The first two arguments are the same as for ``stdio``'s :cfunc:`fopen`:
730 *filename* is the file name to be opened, and *mode* is a string indicating how
731 the file is to be opened.
733 The most commonly-used values of *mode* are ``'r'`` for reading, ``'w'`` for
734 writing (truncating the file if it already exists), and ``'a'`` for appending
735 (which on *some* Unix systems means that *all* writes append to the end of the
736 file regardless of the current seek position). If *mode* is omitted, it
737 defaults to ``'r'``. The default is to use text mode, which may convert
738 ``'\n'`` characters to a platform-specific representation on writing and back
739 on reading. Thus, when opening a binary file, you should append ``'b'`` to
740 the *mode* value to open the file in binary mode, which will improve
741 portability. (Appending ``'b'`` is useful even on systems that don't treat
742 binary and text files differently, where it serves as documentation.) See below
743 for more possible values of *mode*.
746 single: line-buffered I/O
747 single: unbuffered I/O
748 single: buffer size, I/O
749 single: I/O control; buffering
751 The optional *bufsize* argument specifies the file's desired buffer size: 0
752 means unbuffered, 1 means line buffered, any other positive value means use a
753 buffer of (approximately) that size. A negative *bufsize* means to use the
754 system default, which is usually line buffered for tty devices and fully
755 buffered for other files. If omitted, the system default is used. [#]_
757 Modes ``'r+'``, ``'w+'`` and ``'a+'`` open the file for updating (note that
758 ``'w+'`` truncates the file). Append ``'b'`` to the mode to open the file in
759 binary mode, on systems that differentiate between binary and text files; on
760 systems that don't have this distinction, adding the ``'b'`` has no effect.
762 In addition to the standard :cfunc:`fopen` values *mode* may be ``'U'`` or
763 ``'rU'``. Python is usually built with universal newline support; supplying
764 ``'U'`` opens the file as a text file, but lines may be terminated by any of the
765 following: the Unix end-of-line convention ``'\n'``, the Macintosh convention
766 ``'\r'``, or the Windows convention ``'\r\n'``. All of these external
767 representations are seen as ``'\n'`` by the Python program. If Python is built
768 without universal newline support a *mode* with ``'U'`` is the same as normal
769 text mode. Note that file objects so opened also have an attribute called
770 :attr:`newlines` which has a value of ``None`` (if no newlines have yet been
771 seen), ``'\n'``, ``'\r'``, ``'\r\n'``, or a tuple containing all the newline
774 Python enforces that the mode, after stripping ``'U'``, begins with ``'r'``,
777 Python provides many file handling modules including
778 :mod:`fileinput`, :mod:`os`, :mod:`os.path`, :mod:`tempfile`, and
781 .. versionchanged:: 2.5
782 Restriction on first letter of mode string introduced.
787 Given a string of length one, return an integer representing the Unicode code
788 point of the character when the argument is a unicode object, or the value of
789 the byte when the argument is an 8-bit string. For example, ``ord('a')`` returns
790 the integer ``97``, ``ord(u'\u2020')`` returns ``8224``. This is the inverse of
791 :func:`chr` for 8-bit strings and of :func:`unichr` for unicode objects. If a
792 unicode argument is given and Python was built with UCS2 Unicode, then the
793 character's code point must be in the range [0..65535] inclusive; otherwise the
794 string length is two, and a :exc:`TypeError` will be raised.
797 .. function:: pow(x, y[, z])
799 Return *x* to the power *y*; if *z* is present, return *x* to the power *y*,
800 modulo *z* (computed more efficiently than ``pow(x, y) % z``). The two-argument
801 form ``pow(x, y)`` is equivalent to using the power operator: ``x**y``.
803 The arguments must have numeric types. With mixed operand types, the coercion
804 rules for binary arithmetic operators apply. For int and long int operands, the
805 result has the same type as the operands (after coercion) unless the second
806 argument is negative; in that case, all arguments are converted to float and a
807 float result is delivered. For example, ``10**2`` returns ``100``, but
808 ``10**-2`` returns ``0.01``. (This last feature was added in Python 2.2. In
809 Python 2.1 and before, if both arguments were of integer types and the second
810 argument was negative, an exception was raised.) If the second argument is
811 negative, the third argument must be omitted. If *z* is present, *x* and *y*
812 must be of integer types, and *y* must be non-negative. (This restriction was
813 added in Python 2.2. In Python 2.1 and before, floating 3-argument ``pow()``
814 returned platform-dependent results depending on floating-point rounding
818 .. function:: property([fget[, fset[, fdel[, doc]]]])
820 Return a property attribute for :term:`new-style class`\es (classes that
821 derive from :class:`object`).
823 *fget* is a function for getting an attribute value, likewise *fset* is a
824 function for setting, and *fdel* a function for del'ing, an attribute. Typical
825 use is to define a managed attribute x::
828 def __init__(self): self._x = None
829 def getx(self): return self._x
830 def setx(self, value): self._x = value
831 def delx(self): del self._x
832 x = property(getx, setx, delx, "I'm the 'x' property.")
834 If given, *doc* will be the docstring of the property attribute. Otherwise, the
835 property will copy *fget*'s docstring (if it exists). This makes it possible to
836 create read-only properties easily using :func:`property` as a :term:`decorator`::
838 class Parrot(object):
840 self._voltage = 100000
844 """Get the current voltage."""
847 turns the :meth:`voltage` method into a "getter" for a read-only attribute with
850 .. versionadded:: 2.2
852 .. versionchanged:: 2.5
853 Use *fget*'s docstring if no *doc* given.
856 .. function:: range([start,] stop[, step])
858 This is a versatile function to create lists containing arithmetic progressions.
859 It is most often used in :keyword:`for` loops. The arguments must be plain
860 integers. If the *step* argument is omitted, it defaults to ``1``. If the
861 *start* argument is omitted, it defaults to ``0``. The full form returns a list
862 of plain integers ``[start, start + step, start + 2 * step, ...]``. If *step*
863 is positive, the last element is the largest ``start + i * step`` less than
864 *stop*; if *step* is negative, the last element is the smallest ``start + i *
865 step`` greater than *stop*. *step* must not be zero (or else :exc:`ValueError`
866 is raised). Example::
869 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
871 [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
873 [0, 5, 10, 15, 20, 25]
876 >>> range(0, -10, -1)
877 [0, -1, -2, -3, -4, -5, -6, -7, -8, -9]
884 .. function:: raw_input([prompt])
886 If the *prompt* argument is present, it is written to standard output without a
887 trailing newline. The function then reads a line from input, converts it to a
888 string (stripping a trailing newline), and returns that. When EOF is read,
889 :exc:`EOFError` is raised. Example::
891 >>> s = raw_input('--> ')
892 --> Monty Python's Flying Circus
894 "Monty Python's Flying Circus"
896 If the :mod:`readline` module was loaded, then :func:`raw_input` will use it to
897 provide elaborate line editing and history features.
900 .. function:: reduce(function, iterable[, initializer])
902 Apply *function* of two arguments cumulatively to the items of *iterable*, from
903 left to right, so as to reduce the iterable to a single value. For example,
904 ``reduce(lambda x, y: x+y, [1, 2, 3, 4, 5])`` calculates ``((((1+2)+3)+4)+5)``.
905 The left argument, *x*, is the accumulated value and the right argument, *y*, is
906 the update value from the *iterable*. If the optional *initializer* is present,
907 it is placed before the items of the iterable in the calculation, and serves as
908 a default when the iterable is empty. If *initializer* is not given and
909 *iterable* contains only one item, the first item is returned.
912 .. function:: reload(module)
914 Reload a previously imported *module*. The argument must be a module object, so
915 it must have been successfully imported before. This is useful if you have
916 edited the module source file using an external editor and want to try out the
917 new version without leaving the Python interpreter. The return value is the
918 module object (the same as the *module* argument).
920 When ``reload(module)`` is executed:
922 * Python modules' code is recompiled and the module-level code reexecuted,
923 defining a new set of objects which are bound to names in the module's
924 dictionary. The ``init`` function of extension modules is not called a second
927 * As with all other objects in Python the old objects are only reclaimed after
928 their reference counts drop to zero.
930 * The names in the module namespace are updated to point to any new or changed
933 * Other references to the old objects (such as names external to the module) are
934 not rebound to refer to the new objects and must be updated in each namespace
935 where they occur if that is desired.
937 There are a number of other caveats:
939 If a module is syntactically correct but its initialization fails, the first
940 :keyword:`import` statement for it does not bind its name locally, but does
941 store a (partially initialized) module object in ``sys.modules``. To reload the
942 module you must first :keyword:`import` it again (this will bind the name to the
943 partially initialized module object) before you can :func:`reload` it.
945 When a module is reloaded, its dictionary (containing the module's global
946 variables) is retained. Redefinitions of names will override the old
947 definitions, so this is generally not a problem. If the new version of a module
948 does not define a name that was defined by the old version, the old definition
949 remains. This feature can be used to the module's advantage if it maintains a
950 global table or cache of objects --- with a :keyword:`try` statement it can test
951 for the table's presence and skip its initialization if desired::
958 It is legal though generally not very useful to reload built-in or dynamically
959 loaded modules, except for :mod:`sys`, :mod:`__main__` and :mod:`__builtin__`.
960 In many cases, however, extension modules are not designed to be initialized
961 more than once, and may fail in arbitrary ways when reloaded.
963 If a module imports objects from another module using :keyword:`from` ...
964 :keyword:`import` ..., calling :func:`reload` for the other module does not
965 redefine the objects imported from it --- one way around this is to re-execute
966 the :keyword:`from` statement, another is to use :keyword:`import` and qualified
967 names (*module*.*name*) instead.
969 If a module instantiates instances of a class, reloading the module that defines
970 the class does not affect the method definitions of the instances --- they
971 continue to use the old class definition. The same is true for derived classes.
974 .. function:: repr(object)
976 Return a string containing a printable representation of an object. This is the
977 same value yielded by conversions (reverse quotes). It is sometimes useful to be
978 able to access this operation as an ordinary function. For many types, this
979 function makes an attempt to return a string that would yield an object with the
980 same value when passed to :func:`eval`.
983 .. function:: reversed(seq)
985 Return a reverse :term:`iterator`. *seq* must be an object which has
986 a :meth:`__reversed__` method or supports the sequence protocol (the
987 :meth:`__len__` method and the :meth:`__getitem__` method with integer
988 arguments starting at ``0``).
990 .. versionadded:: 2.4
992 .. versionchanged:: 2.6
993 Added the possibility to write a custom :meth:`__reversed__` method.
996 .. function:: round(x[, n])
998 Return the floating point value *x* rounded to *n* digits after the decimal
999 point. If *n* is omitted, it defaults to zero. The result is a floating point
1000 number. Values are rounded to the closest multiple of 10 to the power minus
1001 *n*; if two multiples are equally close, rounding is done away from 0 (so. for
1002 example, ``round(0.5)`` is ``1.0`` and ``round(-0.5)`` is ``-1.0``).
1005 .. function:: set([iterable])
1008 Return a new set, optionally with elements are taken from *iterable*.
1009 The set type is described in :ref:`types-set`.
1011 For other containers see the built in :class:`dict`, :class:`list`, and
1012 :class:`tuple` classes, and the :mod:`collections` module.
1014 .. versionadded:: 2.4
1017 .. function:: setattr(object, name, value)
1019 This is the counterpart of :func:`getattr`. The arguments are an object, a
1020 string and an arbitrary value. The string may name an existing attribute or a
1021 new attribute. The function assigns the value to the attribute, provided the
1022 object allows it. For example, ``setattr(x, 'foobar', 123)`` is equivalent to
1026 .. function:: slice([start,] stop[, step])
1028 .. index:: single: Numerical Python
1030 Return a :term:`slice` object representing the set of indices specified by
1031 ``range(start, stop, step)``. The *start* and *step* arguments default to
1032 ``None``. Slice objects have read-only data attributes :attr:`start`,
1033 :attr:`stop` and :attr:`step` which merely return the argument values (or their
1034 default). They have no other explicit functionality; however they are used by
1035 Numerical Python and other third party extensions. Slice objects are also
1036 generated when extended indexing syntax is used. For example:
1037 ``a[start:stop:step]`` or ``a[start:stop, i]``.
1040 .. function:: sorted(iterable[, cmp[, key[, reverse]]])
1042 Return a new sorted list from the items in *iterable*.
1044 The optional arguments *cmp*, *key*, and *reverse* have the same meaning as
1045 those for the :meth:`list.sort` method (described in section
1046 :ref:`typesseq-mutable`).
1048 *cmp* specifies a custom comparison function of two arguments (iterable
1049 elements) which should return a negative, zero or positive number depending on
1050 whether the first argument is considered smaller than, equal to, or larger than
1051 the second argument: ``cmp=lambda x,y: cmp(x.lower(), y.lower())``. The default
1054 *key* specifies a function of one argument that is used to extract a comparison
1055 key from each list element: ``key=str.lower``. The default value is ``None``.
1057 *reverse* is a boolean value. If set to ``True``, then the list elements are
1058 sorted as if each comparison were reversed.
1060 In general, the *key* and *reverse* conversion processes are much faster than
1061 specifying an equivalent *cmp* function. This is because *cmp* is called
1062 multiple times for each list element while *key* and *reverse* touch each
1065 .. versionadded:: 2.4
1068 .. function:: staticmethod(function)
1070 Return a static method for *function*.
1072 A static method does not receive an implicit first argument. To declare a static
1073 method, use this idiom::
1077 def f(arg1, arg2, ...): ...
1079 The ``@staticmethod`` form is a function :term:`decorator` -- see the
1080 description of function definitions in :ref:`function` for details.
1082 It can be called either on the class (such as ``C.f()``) or on an instance (such
1083 as ``C().f()``). The instance is ignored except for its class.
1085 Static methods in Python are similar to those found in Java or C++. For a more
1086 advanced concept, see :func:`classmethod` in this section.
1088 For more information on static methods, consult the documentation on the
1089 standard type hierarchy in :ref:`types`.
1091 .. versionadded:: 2.2
1093 .. versionchanged:: 2.4
1094 Function decorator syntax added.
1097 .. function:: str([object])
1099 Return a string containing a nicely printable representation of an object. For
1100 strings, this returns the string itself. The difference with ``repr(object)``
1101 is that ``str(object)`` does not always attempt to return a string that is
1102 acceptable to :func:`eval`; its goal is to return a printable string. If no
1103 argument is given, returns the empty string, ``''``.
1105 For more information on strings see :ref:`typesseq` which describes sequence
1106 functionality (strings are sequences), and also the string-specific methods
1107 described in the :ref:`string-methods` section. To output formatted strings
1108 use template strings or the ``%`` operator described in the
1109 :ref:`string-formatting` section. In addition see the :ref:`stringservices`
1110 section. See also :func:`unicode`.
1113 .. function:: sum(iterable[, start])
1115 Sums *start* and the items of an *iterable* from left to right and returns the
1116 total. *start* defaults to ``0``. The *iterable*'s items are normally numbers,
1117 and are not allowed to be strings. The fast, correct way to concatenate a
1118 sequence of strings is by calling ``''.join(sequence)``. Note that
1119 ``sum(range(n), m)`` is equivalent to ``reduce(operator.add, range(n), m)``
1121 .. versionadded:: 2.3
1124 .. function:: super(type[, object-or-type])
1126 Return the superclass of *type*. If the second argument is omitted the super
1127 object returned is unbound. If the second argument is an object,
1128 ``isinstance(obj, type)`` must be true. If the second argument is a type,
1129 ``issubclass(type2, type)`` must be true. :func:`super` only works for
1130 :term:`new-style class`\es.
1132 A typical use for calling a cooperative superclass method is::
1135 def meth(self, arg):
1136 super(C, self).meth(arg)
1138 Note that :func:`super` is implemented as part of the binding process for
1139 explicit dotted attribute lookups such as ``super(C, self).__getitem__(name)``.
1140 Accordingly, :func:`super` is undefined for implicit lookups using statements or
1141 operators such as ``super(C, self)[name]``.
1143 .. versionadded:: 2.2
1146 .. function:: trunc(x)
1148 Return the :class:`Real` value *x* truncated to an :class:`Integral` (usually
1149 a long integer). Delegates to ``x.__trunc__()``.
1151 .. versionadded:: 2.6
1154 .. function:: tuple([iterable])
1156 Return a tuple whose items are the same and in the same order as *iterable*'s
1157 items. *iterable* may be a sequence, a container that supports iteration, or an
1158 iterator object. If *iterable* is already a tuple, it is returned unchanged.
1159 For instance, ``tuple('abc')`` returns ``('a', 'b', 'c')`` and ``tuple([1, 2,
1160 3])`` returns ``(1, 2, 3)``. If no argument is given, returns a new empty
1163 :class:`tuple` is an immutable sequence type, as documented in
1164 :ref:`typesseq`. For other containers see the built in :class:`dict`,
1165 :class:`list`, and :class:`set` classes, and the :mod:`collections` module.
1168 .. function:: type(object)
1170 .. index:: object: type
1172 Return the type of an *object*. The return value is a type object. The
1173 :func:`isinstance` built-in function is recommended for testing the type of an
1176 With three arguments, :func:`type` functions as a constructor as detailed below.
1179 .. function:: type(name, bases, dict)
1182 Return a new type object. This is essentially a dynamic form of the
1183 :keyword:`class` statement. The *name* string is the class name and becomes the
1184 :attr:`__name__` attribute; the *bases* tuple itemizes the base classes and
1185 becomes the :attr:`__bases__` attribute; and the *dict* dictionary is the
1186 namespace containing definitions for class body and becomes the :attr:`__dict__`
1187 attribute. For example, the following two statements create identical
1188 :class:`type` objects::
1190 >>> class X(object):
1193 >>> X = type('X', (object,), dict(a=1))
1195 .. versionadded:: 2.2
1198 .. function:: unichr(i)
1200 Return the Unicode string of one character whose Unicode code is the integer
1201 *i*. For example, ``unichr(97)`` returns the string ``u'a'``. This is the
1202 inverse of :func:`ord` for Unicode strings. The valid range for the argument
1203 depends how Python was configured -- it may be either UCS2 [0..0xFFFF] or UCS4
1204 [0..0x10FFFF]. :exc:`ValueError` is raised otherwise. For ASCII and 8-bit
1205 strings see :func:`chr`.
1207 .. versionadded:: 2.0
1210 .. function:: unicode([object[, encoding [, errors]]])
1212 Return the Unicode string version of *object* using one of the following modes:
1214 If *encoding* and/or *errors* are given, ``unicode()`` will decode the object
1215 which can either be an 8-bit string or a character buffer using the codec for
1216 *encoding*. The *encoding* parameter is a string giving the name of an encoding;
1217 if the encoding is not known, :exc:`LookupError` is raised. Error handling is
1218 done according to *errors*; this specifies the treatment of characters which are
1219 invalid in the input encoding. If *errors* is ``'strict'`` (the default), a
1220 :exc:`ValueError` is raised on errors, while a value of ``'ignore'`` causes
1221 errors to be silently ignored, and a value of ``'replace'`` causes the official
1222 Unicode replacement character, ``U+FFFD``, to be used to replace input
1223 characters which cannot be decoded. See also the :mod:`codecs` module.
1225 If no optional parameters are given, ``unicode()`` will mimic the behaviour of
1226 ``str()`` except that it returns Unicode strings instead of 8-bit strings. More
1227 precisely, if *object* is a Unicode string or subclass it will return that
1228 Unicode string without any additional decoding applied.
1230 For objects which provide a :meth:`__unicode__` method, it will call this method
1231 without arguments to create a Unicode string. For all other objects, the 8-bit
1232 string version or representation is requested and then converted to a Unicode
1233 string using the codec for the default encoding in ``'strict'`` mode.
1235 For more information on Unicode strings see :ref:`typesseq` which describes
1236 sequence functionality (Unicode strings are sequences), and also the
1237 string-specific methods described in the :ref:`string-methods` section. To
1238 output formatted strings use template strings or the ``%`` operator described
1239 in the :ref:`string-formatting` section. In addition see the
1240 :ref:`stringservices` section. See also :func:`str`.
1242 .. versionadded:: 2.0
1244 .. versionchanged:: 2.2
1245 Support for :meth:`__unicode__` added.
1248 .. function:: vars([object])
1250 Without arguments, return a dictionary corresponding to the current local symbol
1251 table. With a module, class or class instance object as argument (or anything
1252 else that has a :attr:`__dict__` attribute), returns a dictionary corresponding
1253 to the object's symbol table. The returned dictionary should not be modified:
1254 the effects on the corresponding symbol table are undefined. [#]_
1257 .. function:: xrange([start,] stop[, step])
1259 This function is very similar to :func:`range`, but returns an "xrange object"
1260 instead of a list. This is an opaque sequence type which yields the same values
1261 as the corresponding list, without actually storing them all simultaneously.
1262 The advantage of :func:`xrange` over :func:`range` is minimal (since
1263 :func:`xrange` still has to create the values when asked for them) except when a
1264 very large range is used on a memory-starved machine or when all of the range's
1265 elements are never used (such as when the loop is usually terminated with
1270 :func:`xrange` is intended to be simple and fast. Implementations may impose
1271 restrictions to achieve this. The C implementation of Python restricts all
1272 arguments to native C longs ("short" Python integers), and also requires that
1273 the number of elements fit in a native C long.
1276 .. function:: zip([iterable, ...])
1278 This function returns a list of tuples, where the *i*-th tuple contains the
1279 *i*-th element from each of the argument sequences or iterables. The returned
1280 list is truncated in length to the length of the shortest argument sequence.
1281 When there are multiple arguments which are all of the same length, :func:`zip`
1282 is similar to :func:`map` with an initial argument of ``None``. With a single
1283 sequence argument, it returns a list of 1-tuples. With no arguments, it returns
1286 .. versionadded:: 2.0
1288 .. versionchanged:: 2.4
1289 Formerly, :func:`zip` required at least one argument and ``zip()`` raised a
1290 :exc:`TypeError` instead of returning an empty list.
1292 .. ---------------------------------------------------------------------------
1295 .. _non-essential-built-in-funcs:
1297 Non-essential Built-in Functions
1298 ================================
1300 There are several built-in functions that are no longer essential to learn, know
1301 or use in modern Python programming. They have been kept here to maintain
1302 backwards compatibility with programs written for older versions of Python.
1304 Python programmers, trainers, students and bookwriters should feel free to
1305 bypass these functions without concerns about missing something important.
1308 .. function:: apply(function, args[, keywords])
1310 The *function* argument must be a callable object (a user-defined or built-in
1311 function or method, or a class object) and the *args* argument must be a
1312 sequence. The *function* is called with *args* as the argument list; the number
1313 of arguments is the length of the tuple. If the optional *keywords* argument is
1314 present, it must be a dictionary whose keys are strings. It specifies keyword
1315 arguments to be added to the end of the argument list. Calling :func:`apply` is
1316 different from just calling ``function(args)``, since in that case there is
1317 always exactly one argument. The use of :func:`apply` is exactly equivalent to
1318 ``function(*args, **keywords)``.
1321 Use the extended call syntax with ``*args`` and ``**keywords`` instead.
1324 .. function:: buffer(object[, offset[, size]])
1326 The *object* argument must be an object that supports the buffer call interface
1327 (such as strings, arrays, and buffers). A new buffer object will be created
1328 which references the *object* argument. The buffer object will be a slice from
1329 the beginning of *object* (or from the specified *offset*). The slice will
1330 extend to the end of *object* (or will have a length given by the *size*
1334 .. function:: coerce(x, y)
1336 Return a tuple consisting of the two numeric arguments converted to a common
1337 type, using the same rules as used by arithmetic operations. If coercion is not
1338 possible, raise :exc:`TypeError`.
1341 .. function:: intern(string)
1343 Enter *string* in the table of "interned" strings and return the interned string
1344 -- which is *string* itself or a copy. Interning strings is useful to gain a
1345 little performance on dictionary lookup -- if the keys in a dictionary are
1346 interned, and the lookup key is interned, the key comparisons (after hashing)
1347 can be done by a pointer compare instead of a string compare. Normally, the
1348 names used in Python programs are automatically interned, and the dictionaries
1349 used to hold module, class or instance attributes have interned keys.
1351 .. versionchanged:: 2.3
1352 Interned strings are not immortal (like they used to be in Python 2.2 and
1353 before); you must keep a reference to the return value of :func:`intern` around
1356 .. rubric:: Footnotes
1358 .. [#] It is used relatively rarely so does not warrant being made into a statement.
1360 .. [#] Specifying a buffer size currently has no effect on systems that don't have
1361 :cfunc:`setvbuf`. The interface to specify the buffer size is not done using a
1362 method that calls :cfunc:`setvbuf`, because that may dump core when called after
1363 any I/O has been performed, and there's no reliable way to determine whether
1366 .. [#] In the current implementation, local variable bindings cannot normally be
1367 affected this way, but variables retrieved from other scopes (such as modules)
1368 can be. This may change.