7 The Python interpreter has a number of functions built into it that are always
8 available. They are listed here in alphabetical order.
13 Return the absolute value of a number. The argument may be a plain or long
14 integer or a floating point number. If the argument is a complex number, its
15 magnitude is returned.
18 .. function:: all(iterable)
20 Return True if all elements of the *iterable* are true (or if the iterable
21 is empty). Equivalent to::
24 for element in iterable:
32 .. function:: any(iterable)
34 Return True if any element of the *iterable* is true. If the iterable
35 is empty, return False. Equivalent to::
38 for element in iterable:
46 .. function:: basestring()
48 This abstract type is the superclass for :class:`str` and :class:`unicode`. It
49 cannot be called or instantiated, but it can be used to test whether an object
50 is an instance of :class:`str` or :class:`unicode`. ``isinstance(obj,
51 basestring)`` is equivalent to ``isinstance(obj, (str, unicode))``.
58 Convert an integer number to a binary string. The result is a valid Python
59 expression. If *x* is not a Python :class:`int` object, it has to define an
60 :meth:`__index__` method that returns an integer.
65 .. function:: bool([x])
67 Convert a value to a Boolean, using the standard truth testing procedure. If
68 *x* is false or omitted, this returns :const:`False`; otherwise it returns
69 :const:`True`. :class:`bool` is also a class, which is a subclass of
70 :class:`int`. Class :class:`bool` cannot be subclassed further. Its only
71 instances are :const:`False` and :const:`True`.
73 .. index:: pair: Boolean; type
75 .. versionadded:: 2.2.1
77 .. versionchanged:: 2.3
78 If no argument is given, this function returns :const:`False`.
81 .. function:: callable(object)
83 Return :const:`True` if the *object* argument appears callable,
84 :const:`False` if not. If this
85 returns true, it is still possible that a call fails, but if it is false,
86 calling *object* will never succeed. Note that classes are callable (calling a
87 class returns a new instance); class instances are callable if they have a
88 :meth:`__call__` method.
93 Return a string of one character whose ASCII code is the integer *i*. For
94 example, ``chr(97)`` returns the string ``'a'``. This is the inverse of
95 :func:`ord`. The argument must be in the range [0..255], inclusive;
96 :exc:`ValueError` will be raised if *i* is outside that range. See
100 .. function:: classmethod(function)
102 Return a class method for *function*.
104 A class method receives the class as implicit first argument, just like an
105 instance method receives the instance. To declare a class method, use this
110 def f(cls, arg1, arg2, ...): ...
112 The ``@classmethod`` form is a function :term:`decorator` -- see the description
113 of function definitions in :ref:`function` for details.
115 It can be called either on the class (such as ``C.f()``) or on an instance (such
116 as ``C().f()``). The instance is ignored except for its class. If a class
117 method is called for a derived class, the derived class object is passed as the
118 implied first argument.
120 Class methods are different than C++ or Java static methods. If you want those,
121 see :func:`staticmethod` in this section.
123 For more information on class methods, consult the documentation on the standard
124 type hierarchy in :ref:`types`.
126 .. versionadded:: 2.2
128 .. versionchanged:: 2.4
129 Function decorator syntax added.
132 .. function:: cmp(x, y)
134 Compare the two objects *x* and *y* and return an integer according to the
135 outcome. The return value is negative if ``x < y``, zero if ``x == y`` and
136 strictly positive if ``x > y``.
139 .. function:: compile(source, filename, mode[, flags[, dont_inherit]])
141 Compile the *source* into a code or AST object. Code objects can be executed
142 by an :keyword:`exec` statement or evaluated by a call to :func:`eval`.
143 *source* can either be a string or an AST object. Refer to the :mod:`ast`
144 module documentation for information on how to work with AST objects.
146 The *filename* argument should give the file from which the code was read;
147 pass some recognizable value if it wasn't read from a file (``'<string>'`` is
150 The *mode* argument specifies what kind of code must be compiled; it can be
151 ``'exec'`` if *source* consists of a sequence of statements, ``'eval'`` if it
152 consists of a single expression, or ``'single'`` if it consists of a single
153 interactive statement (in the latter case, expression statements that
154 evaluate to something other than ``None`` will be printed).
156 The optional arguments *flags* and *dont_inherit* control which future
157 statements (see :pep:`236`) affect the compilation of *source*. If neither
158 is present (or both are zero) the code is compiled with those future
159 statements that are in effect in the code that is calling compile. If the
160 *flags* argument is given and *dont_inherit* is not (or is zero) then the
161 future statements specified by the *flags* argument are used in addition to
162 those that would be used anyway. If *dont_inherit* is a non-zero integer then
163 the *flags* argument is it -- the future statements in effect around the call
164 to compile are ignored.
166 Future statements are specified by bits which can be bitwise ORed together to
167 specify multiple statements. The bitfield required to specify a given feature
168 can be found as the :attr:`compiler_flag` attribute on the :class:`_Feature`
169 instance in the :mod:`__future__` module.
171 This function raises :exc:`SyntaxError` if the compiled source is invalid,
172 and :exc:`TypeError` if the source contains null bytes.
176 When compiling a string with multi-line statements, line endings must be
177 represented by a single newline character (``'\n'``), and the input must
178 be terminated by at least one newline character. If line endings are
179 represented by ``'\r\n'``, use :meth:`str.replace` to change them into
182 .. versionchanged:: 2.3
183 The *flags* and *dont_inherit* arguments were added.
185 .. versionchanged:: 2.6
186 Support for compiling AST objects.
189 .. function:: complex([real[, imag]])
191 Create a complex number with the value *real* + *imag*\*j or convert a string or
192 number to a complex number. If the first parameter is a string, it will be
193 interpreted as a complex number and the function must be called without a second
194 parameter. The second parameter can never be a string. Each argument may be any
195 numeric type (including complex). If *imag* is omitted, it defaults to zero and
196 the function serves as a numeric conversion function like :func:`int`,
197 :func:`long` and :func:`float`. If both arguments are omitted, returns ``0j``.
199 The complex type is described in :ref:`typesnumeric`.
202 .. function:: delattr(object, name)
204 This is a relative of :func:`setattr`. The arguments are an object and a
205 string. The string must be the name of one of the object's attributes. The
206 function deletes the named attribute, provided the object allows it. For
207 example, ``delattr(x, 'foobar')`` is equivalent to ``del x.foobar``.
210 .. function:: dict([arg])
213 Create a new data dictionary, optionally with items taken from *arg*.
214 The dictionary type is described in :ref:`typesmapping`.
216 For other containers see the built in :class:`list`, :class:`set`, and
217 :class:`tuple` classes, and the :mod:`collections` module.
220 .. function:: dir([object])
222 Without arguments, return the list of names in the current local scope. With an
223 argument, attempt to return a list of valid attributes for that object.
225 If the object has a method named :meth:`__dir__`, this method will be called and
226 must return the list of attributes. This allows objects that implement a custom
227 :func:`__getattr__` or :func:`__getattribute__` function to customize the way
228 :func:`dir` reports their attributes.
230 If the object does not provide :meth:`__dir__`, the function tries its best to
231 gather information from the object's :attr:`__dict__` attribute, if defined, and
232 from its type object. The resulting list is not necessarily complete, and may
233 be inaccurate when the object has a custom :func:`__getattr__`.
235 The default :func:`dir` mechanism behaves differently with different types of
236 objects, as it attempts to produce the most relevant, rather than complete,
239 * If the object is a module object, the list contains the names of the module's
242 * If the object is a type or class object, the list contains the names of its
243 attributes, and recursively of the attributes of its bases.
245 * Otherwise, the list contains the object's attributes' names, the names of its
246 class's attributes, and recursively of the attributes of its class's base
249 The resulting list is sorted alphabetically. For example:
252 >>> dir() # doctest: +SKIP
253 ['__builtins__', '__doc__', '__name__', 'struct']
254 >>> dir(struct) # doctest: +NORMALIZE_WHITESPACE
255 ['Struct', '__builtins__', '__doc__', '__file__', '__name__',
256 '__package__', '_clearcache', 'calcsize', 'error', 'pack', 'pack_into',
257 'unpack', 'unpack_from']
258 >>> class Foo(object):
259 ... def __dir__(self):
260 ... return ["kan", "ga", "roo"]
268 Because :func:`dir` is supplied primarily as a convenience for use at an
269 interactive prompt, it tries to supply an interesting set of names more than it
270 tries to supply a rigorously or consistently defined set of names, and its
271 detailed behavior may change across releases. For example, metaclass attributes
272 are not in the result list when the argument is a class.
275 .. function:: divmod(a, b)
277 Take two (non complex) numbers as arguments and return a pair of numbers
278 consisting of their quotient and remainder when using long division. With mixed
279 operand types, the rules for binary arithmetic operators apply. For plain and
280 long integers, the result is the same as ``(a // b, a % b)``. For floating point
281 numbers the result is ``(q, a % b)``, where *q* is usually ``math.floor(a / b)``
282 but may be 1 less than that. In any case ``q * b + a % b`` is very close to
283 *a*, if ``a % b`` is non-zero it has the same sign as *b*, and ``0 <= abs(a % b)
286 .. versionchanged:: 2.3
287 Using :func:`divmod` with complex numbers is deprecated.
290 .. function:: enumerate(sequence[, start=0])
292 Return an enumerate object. *sequence* must be a sequence, an
293 :term:`iterator`, or some other object which supports iteration. The
294 :meth:`!next` method of the iterator returned by :func:`enumerate` returns a
295 tuple containing a count (from *start* which defaults to 0) and the
296 corresponding value obtained from iterating over *iterable*.
297 :func:`enumerate` is useful for obtaining an indexed series: ``(0, seq[0])``,
298 ``(1, seq[1])``, ``(2, seq[2])``, .... For example:
300 >>> for i, season in enumerate(['Spring', 'Summer', 'Fall', 'Winter']):
307 .. versionadded:: 2.3
308 .. versionadded:: 2.6
309 The *start* parameter.
312 .. function:: eval(expression[, globals[, locals]])
314 The arguments are a string and optional globals and locals. If provided,
315 *globals* must be a dictionary. If provided, *locals* can be any mapping
318 .. versionchanged:: 2.4
319 formerly *locals* was required to be a dictionary.
321 The *expression* argument is parsed and evaluated as a Python expression
322 (technically speaking, a condition list) using the *globals* and *locals*
323 dictionaries as global and local namespace. If the *globals* dictionary is
324 present and lacks '__builtins__', the current globals are copied into *globals*
325 before *expression* is parsed. This means that *expression* normally has full
326 access to the standard :mod:`__builtin__` module and restricted environments are
327 propagated. If the *locals* dictionary is omitted it defaults to the *globals*
328 dictionary. If both dictionaries are omitted, the expression is executed in the
329 environment where :func:`eval` is called. The return value is the result of
330 the evaluated expression. Syntax errors are reported as exceptions. Example:
333 >>> print eval('x+1')
336 This function can also be used to execute arbitrary code objects (such as
337 those created by :func:`compile`). In this case pass a code object instead
338 of a string. If the code object has been compiled with ``'exec'`` as the
339 *kind* argument, :func:`eval`\'s return value will be ``None``.
341 Hints: dynamic execution of statements is supported by the :keyword:`exec`
342 statement. Execution of statements from a file is supported by the
343 :func:`execfile` function. The :func:`globals` and :func:`locals` functions
344 returns the current global and local dictionary, respectively, which may be
345 useful to pass around for use by :func:`eval` or :func:`execfile`.
348 .. function:: execfile(filename[, globals[, locals]])
350 This function is similar to the :keyword:`exec` statement, but parses a file
351 instead of a string. It is different from the :keyword:`import` statement in
352 that it does not use the module administration --- it reads the file
353 unconditionally and does not create a new module. [#]_
355 The arguments are a file name and two optional dictionaries. The file is parsed
356 and evaluated as a sequence of Python statements (similarly to a module) using
357 the *globals* and *locals* dictionaries as global and local namespace. If
358 provided, *locals* can be any mapping object.
360 .. versionchanged:: 2.4
361 formerly *locals* was required to be a dictionary.
363 If the *locals* dictionary is omitted it defaults to the *globals* dictionary.
364 If both dictionaries are omitted, the expression is executed in the environment
365 where :func:`execfile` is called. The return value is ``None``.
369 The default *locals* act as described for function :func:`locals` below:
370 modifications to the default *locals* dictionary should not be attempted. Pass
371 an explicit *locals* dictionary if you need to see effects of the code on
372 *locals* after function :func:`execfile` returns. :func:`execfile` cannot be
373 used reliably to modify a function's locals.
376 .. function:: file(filename[, mode[, bufsize]])
378 Constructor function for the :class:`file` type, described further in section
379 :ref:`bltin-file-objects`. The constructor's arguments are the same as those
380 of the :func:`open` built-in function described below.
382 When opening a file, it's preferable to use :func:`open` instead of invoking
383 this constructor directly. :class:`file` is more suited to type testing (for
384 example, writing ``isinstance(f, file)``).
386 .. versionadded:: 2.2
389 .. function:: filter(function, iterable)
391 Construct a list from those elements of *iterable* for which *function* returns
392 true. *iterable* may be either a sequence, a container which supports
393 iteration, or an iterator. If *iterable* is a string or a tuple, the result
394 also has that type; otherwise it is always a list. If *function* is ``None``,
395 the identity function is assumed, that is, all elements of *iterable* that are
398 Note that ``filter(function, iterable)`` is equivalent to ``[item for item in
399 iterable if function(item)]`` if function is not ``None`` and ``[item for item
400 in iterable if item]`` if function is ``None``.
402 See :func:`itertools.filterfalse` for the complementary function that returns
403 elements of *iterable* for which *function* returns false.
406 .. function:: float([x])
408 Convert a string or a number to floating point. If the argument is a string, it
409 must contain a possibly signed decimal or floating point number, possibly
410 embedded in whitespace. The argument may also be [+|-]nan or [+|-]inf.
411 Otherwise, the argument may be a plain or long integer
412 or a floating point number, and a floating point number with the same value
413 (within Python's floating point precision) is returned. If no argument is
414 given, returns ``0.0``.
422 When passing in a string, values for NaN and Infinity may be returned, depending
423 on the underlying C library. Float accepts the strings nan, inf and -inf for
424 NaN and positive or negative infinity. The case and a leading + are ignored as
425 well as a leading - is ignored for NaN. Float always represents NaN and infinity
428 The float type is described in :ref:`typesnumeric`.
431 .. function:: format(value[, format_spec])
437 Convert a *value* to a "formatted" representation, as controlled by
438 *format_spec*. The interpretation of *format_spec* will depend on the type
439 of the *value* argument, however there is a standard formatting syntax that
440 is used by most built-in types: :ref:`formatspec`.
444 ``format(value, format_spec)`` merely calls
445 ``value.__format__(format_spec)``.
447 .. versionadded:: 2.6
450 .. function:: frozenset([iterable])
453 Return a frozenset object, optionally with elements taken from *iterable*.
454 The frozenset type is described in :ref:`types-set`.
456 For other containers see the built in :class:`dict`, :class:`list`, and
457 :class:`tuple` classes, and the :mod:`collections` module.
459 .. versionadded:: 2.4
462 .. function:: getattr(object, name[, default])
464 Return the value of the named attributed of *object*. *name* must be a string.
465 If the string is the name of one of the object's attributes, the result is the
466 value of that attribute. For example, ``getattr(x, 'foobar')`` is equivalent to
467 ``x.foobar``. If the named attribute does not exist, *default* is returned if
468 provided, otherwise :exc:`AttributeError` is raised.
471 .. function:: globals()
473 Return a dictionary representing the current global symbol table. This is always
474 the dictionary of the current module (inside a function or method, this is the
475 module where it is defined, not the module from which it is called).
478 .. function:: hasattr(object, name)
480 The arguments are an object and a string. The result is ``True`` if the string
481 is the name of one of the object's attributes, ``False`` if not. (This is
482 implemented by calling ``getattr(object, name)`` and seeing whether it raises an
486 .. function:: hash(object)
488 Return the hash value of the object (if it has one). Hash values are integers.
489 They are used to quickly compare dictionary keys during a dictionary lookup.
490 Numeric values that compare equal have the same hash value (even if they are of
491 different types, as is the case for 1 and 1.0).
494 .. function:: help([object])
496 Invoke the built-in help system. (This function is intended for interactive
497 use.) If no argument is given, the interactive help system starts on the
498 interpreter console. If the argument is a string, then the string is looked up
499 as the name of a module, function, class, method, keyword, or documentation
500 topic, and a help page is printed on the console. If the argument is any other
501 kind of object, a help page on the object is generated.
503 This function is added to the built-in namespace by the :mod:`site` module.
505 .. versionadded:: 2.2
510 Convert an integer number (of any size) to a hexadecimal string. The result is a
511 valid Python expression.
515 To obtain a hexadecimal string representation for a float, use the
516 :meth:`float.hex` method.
518 .. versionchanged:: 2.4
519 Formerly only returned an unsigned literal.
522 .. function:: id(object)
524 Return the "identity" of an object. This is an integer (or long integer) which
525 is guaranteed to be unique and constant for this object during its lifetime.
526 Two objects with non-overlapping lifetimes may have the same :func:`id`
529 .. impl-detail:: This is the address of the object.
532 .. function:: input([prompt])
534 Equivalent to ``eval(raw_input(prompt))``.
538 This function is not safe from user errors! It expects a valid Python
539 expression as input; if the input is not syntactically valid, a
540 :exc:`SyntaxError` will be raised. Other exceptions may be raised if there is an
541 error during evaluation. (On the other hand, sometimes this is exactly what you
542 need when writing a quick script for expert use.)
544 If the :mod:`readline` module was loaded, then :func:`input` will use it to
545 provide elaborate line editing and history features.
547 Consider using the :func:`raw_input` function for general input from users.
550 .. function:: int([x[, base]])
552 Convert a string or number to a plain integer. If the argument is a string,
553 it must contain a possibly signed decimal number representable as a Python
554 integer, possibly embedded in whitespace. The *base* parameter gives the
555 base for the conversion (which is 10 by default) and may be any integer in
556 the range [2, 36], or zero. If *base* is zero, the proper radix is
557 determined based on the contents of string; the interpretation is the same as
558 for integer literals. (See :ref:`numbers`.) If *base* is specified and *x*
559 is not a string, :exc:`TypeError` is raised. Otherwise, the argument may be a
560 plain or long integer or a floating point number. Conversion of floating
561 point numbers to integers truncates (towards zero). If the argument is
562 outside the integer range a long object will be returned instead. If no
563 arguments are given, returns ``0``.
565 The integer type is described in :ref:`typesnumeric`.
568 .. function:: isinstance(object, classinfo)
570 Return true if the *object* argument is an instance of the *classinfo* argument,
571 or of a (direct or indirect) subclass thereof. Also return true if *classinfo*
572 is a type object (new-style class) and *object* is an object of that type or of
573 a (direct or indirect) subclass thereof. If *object* is not a class instance or
574 an object of the given type, the function always returns false. If *classinfo*
575 is neither a class object nor a type object, it may be a tuple of class or type
576 objects, or may recursively contain other such tuples (other sequence types are
577 not accepted). If *classinfo* is not a class, type, or tuple of classes, types,
578 and such tuples, a :exc:`TypeError` exception is raised.
580 .. versionchanged:: 2.2
581 Support for a tuple of type information was added.
584 .. function:: issubclass(class, classinfo)
586 Return true if *class* is a subclass (direct or indirect) of *classinfo*. A
587 class is considered a subclass of itself. *classinfo* may be a tuple of class
588 objects, in which case every entry in *classinfo* will be checked. In any other
589 case, a :exc:`TypeError` exception is raised.
591 .. versionchanged:: 2.3
592 Support for a tuple of type information was added.
595 .. function:: iter(o[, sentinel])
597 Return an :term:`iterator` object. The first argument is interpreted very differently
598 depending on the presence of the second argument. Without a second argument, *o*
599 must be a collection object which supports the iteration protocol (the
600 :meth:`__iter__` method), or it must support the sequence protocol (the
601 :meth:`__getitem__` method with integer arguments starting at ``0``). If it
602 does not support either of those protocols, :exc:`TypeError` is raised. If the
603 second argument, *sentinel*, is given, then *o* must be a callable object. The
604 iterator created in this case will call *o* with no arguments for each call to
605 its :meth:`~iterator.next` method; if the value returned is equal to *sentinel*,
606 :exc:`StopIteration` will be raised, otherwise the value will be returned.
608 One useful application of the second form of :func:`iter` is to read lines of
609 a file until a certain line is reached. The following example reads a file
610 until ``"STOP"`` is reached: ::
612 with open("mydata.txt") as fp:
613 for line in iter(fp.readline, "STOP"):
616 .. versionadded:: 2.2
621 Return the length (the number of items) of an object. The argument may be a
622 sequence (string, tuple or list) or a mapping (dictionary).
625 .. function:: list([iterable])
627 Return a list whose items are the same and in the same order as *iterable*'s
628 items. *iterable* may be either a sequence, a container that supports
629 iteration, or an iterator object. If *iterable* is already a list, a copy is
630 made and returned, similar to ``iterable[:]``. For instance, ``list('abc')``
631 returns ``['a', 'b', 'c']`` and ``list( (1, 2, 3) )`` returns ``[1, 2, 3]``. If
632 no argument is given, returns a new empty list, ``[]``.
634 :class:`list` is a mutable sequence type, as documented in
635 :ref:`typesseq`. For other containers see the built in :class:`dict`,
636 :class:`set`, and :class:`tuple` classes, and the :mod:`collections` module.
639 .. function:: locals()
641 Update and return a dictionary representing the current local symbol table.
642 Free variables are returned by :func:`locals` when it is called in function
643 blocks, but not in class blocks.
647 The contents of this dictionary should not be modified; changes may not
648 affect the values of local and free variables used by the interpreter.
651 .. function:: long([x[, base]])
653 Convert a string or number to a long integer. If the argument is a string, it
654 must contain a possibly signed number of arbitrary size, possibly embedded in
655 whitespace. The *base* argument is interpreted in the same way as for
656 :func:`int`, and may only be given when *x* is a string. Otherwise, the argument
657 may be a plain or long integer or a floating point number, and a long integer
658 with the same value is returned. Conversion of floating point numbers to
659 integers truncates (towards zero). If no arguments are given, returns ``0L``.
661 The long type is described in :ref:`typesnumeric`.
664 .. function:: map(function, iterable, ...)
666 Apply *function* to every item of *iterable* and return a list of the results.
667 If additional *iterable* arguments are passed, *function* must take that many
668 arguments and is applied to the items from all iterables in parallel. If one
669 iterable is shorter than another it is assumed to be extended with ``None``
670 items. If *function* is ``None``, the identity function is assumed; if there
671 are multiple arguments, :func:`map` returns a list consisting of tuples
672 containing the corresponding items from all iterables (a kind of transpose
673 operation). The *iterable* arguments may be a sequence or any iterable object;
674 the result is always a list.
677 .. function:: max(iterable[, args...][key])
679 With a single argument *iterable*, return the largest item of a non-empty
680 iterable (such as a string, tuple or list). With more than one argument, return
681 the largest of the arguments.
683 The optional *key* argument specifies a one-argument ordering function like that
684 used for :meth:`list.sort`. The *key* argument, if supplied, must be in keyword
685 form (for example, ``max(a,b,c,key=func)``).
687 .. versionchanged:: 2.5
688 Added support for the optional *key* argument.
691 .. function:: memoryview(obj)
694 Return a "memory view" object created from the given argument. See
695 :ref:`typememoryview` for more information.
698 .. function:: min(iterable[, args...][key])
700 With a single argument *iterable*, return the smallest item of a non-empty
701 iterable (such as a string, tuple or list). With more than one argument, return
702 the smallest of the arguments.
704 The optional *key* argument specifies a one-argument ordering function like that
705 used for :meth:`list.sort`. The *key* argument, if supplied, must be in keyword
706 form (for example, ``min(a,b,c,key=func)``).
708 .. versionchanged:: 2.5
709 Added support for the optional *key* argument.
712 .. function:: next(iterator[, default])
714 Retrieve the next item from the *iterator* by calling its
715 :meth:`~iterator.next` method. If *default* is given, it is returned if the
716 iterator is exhausted, otherwise :exc:`StopIteration` is raised.
718 .. versionadded:: 2.6
721 .. function:: object()
723 Return a new featureless object. :class:`object` is a base for all new style
724 classes. It has the methods that are common to all instances of new style
727 .. versionadded:: 2.2
729 .. versionchanged:: 2.3
730 This function does not accept any arguments. Formerly, it accepted arguments but
736 Convert an integer number (of any size) to an octal string. The result is a
737 valid Python expression.
739 .. versionchanged:: 2.4
740 Formerly only returned an unsigned literal.
743 .. function:: open(filename[, mode[, bufsize]])
745 Open a file, returning an object of the :class:`file` type described in
746 section :ref:`bltin-file-objects`. If the file cannot be opened,
747 :exc:`IOError` is raised. When opening a file, it's preferable to use
748 :func:`open` instead of invoking the :class:`file` constructor directly.
750 The first two arguments are the same as for ``stdio``'s :cfunc:`fopen`:
751 *filename* is the file name to be opened, and *mode* is a string indicating how
752 the file is to be opened.
754 The most commonly-used values of *mode* are ``'r'`` for reading, ``'w'`` for
755 writing (truncating the file if it already exists), and ``'a'`` for appending
756 (which on *some* Unix systems means that *all* writes append to the end of the
757 file regardless of the current seek position). If *mode* is omitted, it
758 defaults to ``'r'``. The default is to use text mode, which may convert
759 ``'\n'`` characters to a platform-specific representation on writing and back
760 on reading. Thus, when opening a binary file, you should append ``'b'`` to
761 the *mode* value to open the file in binary mode, which will improve
762 portability. (Appending ``'b'`` is useful even on systems that don't treat
763 binary and text files differently, where it serves as documentation.) See below
764 for more possible values of *mode*.
767 single: line-buffered I/O
768 single: unbuffered I/O
769 single: buffer size, I/O
770 single: I/O control; buffering
772 The optional *bufsize* argument specifies the file's desired buffer size: 0
773 means unbuffered, 1 means line buffered, any other positive value means use a
774 buffer of (approximately) that size. A negative *bufsize* means to use the
775 system default, which is usually line buffered for tty devices and fully
776 buffered for other files. If omitted, the system default is used. [#]_
778 Modes ``'r+'``, ``'w+'`` and ``'a+'`` open the file for updating (note that
779 ``'w+'`` truncates the file). Append ``'b'`` to the mode to open the file in
780 binary mode, on systems that differentiate between binary and text files; on
781 systems that don't have this distinction, adding the ``'b'`` has no effect.
783 In addition to the standard :cfunc:`fopen` values *mode* may be ``'U'`` or
784 ``'rU'``. Python is usually built with universal newline support; supplying
785 ``'U'`` opens the file as a text file, but lines may be terminated by any of the
786 following: the Unix end-of-line convention ``'\n'``, the Macintosh convention
787 ``'\r'``, or the Windows convention ``'\r\n'``. All of these external
788 representations are seen as ``'\n'`` by the Python program. If Python is built
789 without universal newline support a *mode* with ``'U'`` is the same as normal
790 text mode. Note that file objects so opened also have an attribute called
791 :attr:`newlines` which has a value of ``None`` (if no newlines have yet been
792 seen), ``'\n'``, ``'\r'``, ``'\r\n'``, or a tuple containing all the newline
795 Python enforces that the mode, after stripping ``'U'``, begins with ``'r'``,
798 Python provides many file handling modules including
799 :mod:`fileinput`, :mod:`os`, :mod:`os.path`, :mod:`tempfile`, and
802 .. versionchanged:: 2.5
803 Restriction on first letter of mode string introduced.
808 Given a string of length one, return an integer representing the Unicode code
809 point of the character when the argument is a unicode object, or the value of
810 the byte when the argument is an 8-bit string. For example, ``ord('a')`` returns
811 the integer ``97``, ``ord(u'\u2020')`` returns ``8224``. This is the inverse of
812 :func:`chr` for 8-bit strings and of :func:`unichr` for unicode objects. If a
813 unicode argument is given and Python was built with UCS2 Unicode, then the
814 character's code point must be in the range [0..65535] inclusive; otherwise the
815 string length is two, and a :exc:`TypeError` will be raised.
818 .. function:: pow(x, y[, z])
820 Return *x* to the power *y*; if *z* is present, return *x* to the power *y*,
821 modulo *z* (computed more efficiently than ``pow(x, y) % z``). The two-argument
822 form ``pow(x, y)`` is equivalent to using the power operator: ``x**y``.
824 The arguments must have numeric types. With mixed operand types, the coercion
825 rules for binary arithmetic operators apply. For int and long int operands, the
826 result has the same type as the operands (after coercion) unless the second
827 argument is negative; in that case, all arguments are converted to float and a
828 float result is delivered. For example, ``10**2`` returns ``100``, but
829 ``10**-2`` returns ``0.01``. (This last feature was added in Python 2.2. In
830 Python 2.1 and before, if both arguments were of integer types and the second
831 argument was negative, an exception was raised.) If the second argument is
832 negative, the third argument must be omitted. If *z* is present, *x* and *y*
833 must be of integer types, and *y* must be non-negative. (This restriction was
834 added in Python 2.2. In Python 2.1 and before, floating 3-argument ``pow()``
835 returned platform-dependent results depending on floating-point rounding
839 .. function:: print([object, ...][, sep=' '][, end='\\n'][, file=sys.stdout])
841 Print *object*\(s) to the stream *file*, separated by *sep* and followed by
842 *end*. *sep*, *end* and *file*, if present, must be given as keyword
845 All non-keyword arguments are converted to strings like :func:`str` does and
846 written to the stream, separated by *sep* and followed by *end*. Both *sep*
847 and *end* must be strings; they can also be ``None``, which means to use the
848 default values. If no *object* is given, :func:`print` will just write
851 The *file* argument must be an object with a ``write(string)`` method; if it
852 is not present or ``None``, :data:`sys.stdout` will be used.
856 This function is not normally available as a built-in since the name
857 ``print`` is recognized as the :keyword:`print` statement. To disable the
858 statement and use the :func:`print` function, use this future statement at
859 the top of your module::
861 from __future__ import print_function
863 .. versionadded:: 2.6
866 .. function:: property([fget[, fset[, fdel[, doc]]]])
868 Return a property attribute for :term:`new-style class`\es (classes that
869 derive from :class:`object`).
871 *fget* is a function for getting an attribute value, likewise *fset* is a
872 function for setting, and *fdel* a function for del'ing, an attribute. Typical
873 use is to define a managed attribute x::
881 def setx(self, value):
885 x = property(getx, setx, delx, "I'm the 'x' property.")
887 If given, *doc* will be the docstring of the property attribute. Otherwise, the
888 property will copy *fget*'s docstring (if it exists). This makes it possible to
889 create read-only properties easily using :func:`property` as a :term:`decorator`::
891 class Parrot(object):
893 self._voltage = 100000
897 """Get the current voltage."""
900 turns the :meth:`voltage` method into a "getter" for a read-only attribute
903 A property object has :attr:`getter`, :attr:`setter`, and :attr:`deleter`
904 methods usable as decorators that create a copy of the property with the
905 corresponding accessor function set to the decorated function. This is
906 best explained with an example::
914 """I'm the 'x' property."""
925 This code is exactly equivalent to the first example. Be sure to give the
926 additional functions the same name as the original property (``x`` in this
929 The returned property also has the attributes ``fget``, ``fset``, and
930 ``fdel`` corresponding to the constructor arguments.
932 .. versionadded:: 2.2
934 .. versionchanged:: 2.5
935 Use *fget*'s docstring if no *doc* given.
937 .. versionchanged:: 2.6
938 The ``getter``, ``setter``, and ``deleter`` attributes were added.
941 .. function:: range([start,] stop[, step])
943 This is a versatile function to create lists containing arithmetic progressions.
944 It is most often used in :keyword:`for` loops. The arguments must be plain
945 integers. If the *step* argument is omitted, it defaults to ``1``. If the
946 *start* argument is omitted, it defaults to ``0``. The full form returns a list
947 of plain integers ``[start, start + step, start + 2 * step, ...]``. If *step*
948 is positive, the last element is the largest ``start + i * step`` less than
949 *stop*; if *step* is negative, the last element is the smallest ``start + i *
950 step`` greater than *stop*. *step* must not be zero (or else :exc:`ValueError`
954 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
956 [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
958 [0, 5, 10, 15, 20, 25]
961 >>> range(0, -10, -1)
962 [0, -1, -2, -3, -4, -5, -6, -7, -8, -9]
969 .. function:: raw_input([prompt])
971 If the *prompt* argument is present, it is written to standard output without a
972 trailing newline. The function then reads a line from input, converts it to a
973 string (stripping a trailing newline), and returns that. When EOF is read,
974 :exc:`EOFError` is raised. Example::
976 >>> s = raw_input('--> ')
977 --> Monty Python's Flying Circus
979 "Monty Python's Flying Circus"
981 If the :mod:`readline` module was loaded, then :func:`raw_input` will use it to
982 provide elaborate line editing and history features.
985 .. function:: reduce(function, iterable[, initializer])
987 Apply *function* of two arguments cumulatively to the items of *iterable*, from
988 left to right, so as to reduce the iterable to a single value. For example,
989 ``reduce(lambda x, y: x+y, [1, 2, 3, 4, 5])`` calculates ``((((1+2)+3)+4)+5)``.
990 The left argument, *x*, is the accumulated value and the right argument, *y*, is
991 the update value from the *iterable*. If the optional *initializer* is present,
992 it is placed before the items of the iterable in the calculation, and serves as
993 a default when the iterable is empty. If *initializer* is not given and
994 *iterable* contains only one item, the first item is returned.
997 .. function:: reload(module)
999 Reload a previously imported *module*. The argument must be a module object, so
1000 it must have been successfully imported before. This is useful if you have
1001 edited the module source file using an external editor and want to try out the
1002 new version without leaving the Python interpreter. The return value is the
1003 module object (the same as the *module* argument).
1005 When ``reload(module)`` is executed:
1007 * Python modules' code is recompiled and the module-level code reexecuted,
1008 defining a new set of objects which are bound to names in the module's
1009 dictionary. The ``init`` function of extension modules is not called a second
1012 * As with all other objects in Python the old objects are only reclaimed after
1013 their reference counts drop to zero.
1015 * The names in the module namespace are updated to point to any new or changed
1018 * Other references to the old objects (such as names external to the module) are
1019 not rebound to refer to the new objects and must be updated in each namespace
1020 where they occur if that is desired.
1022 There are a number of other caveats:
1024 If a module is syntactically correct but its initialization fails, the first
1025 :keyword:`import` statement for it does not bind its name locally, but does
1026 store a (partially initialized) module object in ``sys.modules``. To reload the
1027 module you must first :keyword:`import` it again (this will bind the name to the
1028 partially initialized module object) before you can :func:`reload` it.
1030 When a module is reloaded, its dictionary (containing the module's global
1031 variables) is retained. Redefinitions of names will override the old
1032 definitions, so this is generally not a problem. If the new version of a module
1033 does not define a name that was defined by the old version, the old definition
1034 remains. This feature can be used to the module's advantage if it maintains a
1035 global table or cache of objects --- with a :keyword:`try` statement it can test
1036 for the table's presence and skip its initialization if desired::
1043 It is legal though generally not very useful to reload built-in or dynamically
1044 loaded modules, except for :mod:`sys`, :mod:`__main__` and :mod:`__builtin__`.
1045 In many cases, however, extension modules are not designed to be initialized
1046 more than once, and may fail in arbitrary ways when reloaded.
1048 If a module imports objects from another module using :keyword:`from` ...
1049 :keyword:`import` ..., calling :func:`reload` for the other module does not
1050 redefine the objects imported from it --- one way around this is to re-execute
1051 the :keyword:`from` statement, another is to use :keyword:`import` and qualified
1052 names (*module*.*name*) instead.
1054 If a module instantiates instances of a class, reloading the module that defines
1055 the class does not affect the method definitions of the instances --- they
1056 continue to use the old class definition. The same is true for derived classes.
1059 .. function:: repr(object)
1061 Return a string containing a printable representation of an object. This is
1062 the same value yielded by conversions (reverse quotes). It is sometimes
1063 useful to be able to access this operation as an ordinary function. For many
1064 types, this function makes an attempt to return a string that would yield an
1065 object with the same value when passed to :func:`eval`, otherwise the
1066 representation is a string enclosed in angle brackets that contains the name
1067 of the type of the object together with additional information often
1068 including the name and address of the object. A class can control what this
1069 function returns for its instances by defining a :meth:`__repr__` method.
1072 .. function:: reversed(seq)
1074 Return a reverse :term:`iterator`. *seq* must be an object which has
1075 a :meth:`__reversed__` method or supports the sequence protocol (the
1076 :meth:`__len__` method and the :meth:`__getitem__` method with integer
1077 arguments starting at ``0``).
1079 .. versionadded:: 2.4
1081 .. versionchanged:: 2.6
1082 Added the possibility to write a custom :meth:`__reversed__` method.
1085 .. function:: round(x[, n])
1087 Return the floating point value *x* rounded to *n* digits after the decimal
1088 point. If *n* is omitted, it defaults to zero. The result is a floating point
1089 number. Values are rounded to the closest multiple of 10 to the power minus
1090 *n*; if two multiples are equally close, rounding is done away from 0 (so. for
1091 example, ``round(0.5)`` is ``1.0`` and ``round(-0.5)`` is ``-1.0``).
1094 .. function:: set([iterable])
1097 Return a new set, optionally with elements are taken from *iterable*.
1098 The set type is described in :ref:`types-set`.
1100 For other containers see the built in :class:`dict`, :class:`list`, and
1101 :class:`tuple` classes, and the :mod:`collections` module.
1103 .. versionadded:: 2.4
1106 .. function:: setattr(object, name, value)
1108 This is the counterpart of :func:`getattr`. The arguments are an object, a
1109 string and an arbitrary value. The string may name an existing attribute or a
1110 new attribute. The function assigns the value to the attribute, provided the
1111 object allows it. For example, ``setattr(x, 'foobar', 123)`` is equivalent to
1115 .. function:: slice([start,] stop[, step])
1117 .. index:: single: Numerical Python
1119 Return a :term:`slice` object representing the set of indices specified by
1120 ``range(start, stop, step)``. The *start* and *step* arguments default to
1121 ``None``. Slice objects have read-only data attributes :attr:`start`,
1122 :attr:`stop` and :attr:`step` which merely return the argument values (or their
1123 default). They have no other explicit functionality; however they are used by
1124 Numerical Python and other third party extensions. Slice objects are also
1125 generated when extended indexing syntax is used. For example:
1126 ``a[start:stop:step]`` or ``a[start:stop, i]``. See :func:`itertools.islice`
1127 for an alternate version that returns an iterator.
1130 .. function:: sorted(iterable[, cmp[, key[, reverse]]])
1132 Return a new sorted list from the items in *iterable*.
1134 The optional arguments *cmp*, *key*, and *reverse* have the same meaning as
1135 those for the :meth:`list.sort` method (described in section
1136 :ref:`typesseq-mutable`).
1138 *cmp* specifies a custom comparison function of two arguments (iterable
1139 elements) which should return a negative, zero or positive number depending on
1140 whether the first argument is considered smaller than, equal to, or larger than
1141 the second argument: ``cmp=lambda x,y: cmp(x.lower(), y.lower())``. The default
1144 *key* specifies a function of one argument that is used to extract a comparison
1145 key from each list element: ``key=str.lower``. The default value is ``None``.
1147 *reverse* is a boolean value. If set to ``True``, then the list elements are
1148 sorted as if each comparison were reversed.
1150 In general, the *key* and *reverse* conversion processes are much faster
1151 than specifying an equivalent *cmp* function. This is because *cmp* is
1152 called multiple times for each list element while *key* and *reverse* touch
1153 each element only once. To convert an old-style *cmp* function to a *key*
1154 function, see the `CmpToKey recipe in the ASPN cookbook
1155 <http://code.activestate.com/recipes/576653/>`_\.
1157 .. versionadded:: 2.4
1160 .. function:: staticmethod(function)
1162 Return a static method for *function*.
1164 A static method does not receive an implicit first argument. To declare a static
1165 method, use this idiom::
1169 def f(arg1, arg2, ...): ...
1171 The ``@staticmethod`` form is a function :term:`decorator` -- see the
1172 description of function definitions in :ref:`function` for details.
1174 It can be called either on the class (such as ``C.f()``) or on an instance (such
1175 as ``C().f()``). The instance is ignored except for its class.
1177 Static methods in Python are similar to those found in Java or C++. For a more
1178 advanced concept, see :func:`classmethod` in this section.
1180 For more information on static methods, consult the documentation on the
1181 standard type hierarchy in :ref:`types`.
1183 .. versionadded:: 2.2
1185 .. versionchanged:: 2.4
1186 Function decorator syntax added.
1189 .. function:: str([object])
1191 Return a string containing a nicely printable representation of an object. For
1192 strings, this returns the string itself. The difference with ``repr(object)``
1193 is that ``str(object)`` does not always attempt to return a string that is
1194 acceptable to :func:`eval`; its goal is to return a printable string. If no
1195 argument is given, returns the empty string, ``''``.
1197 For more information on strings see :ref:`typesseq` which describes sequence
1198 functionality (strings are sequences), and also the string-specific methods
1199 described in the :ref:`string-methods` section. To output formatted strings
1200 use template strings or the ``%`` operator described in the
1201 :ref:`string-formatting` section. In addition see the :ref:`stringservices`
1202 section. See also :func:`unicode`.
1205 .. function:: sum(iterable[, start])
1207 Sums *start* and the items of an *iterable* from left to right and returns the
1208 total. *start* defaults to ``0``. The *iterable*'s items are normally numbers,
1209 and are not allowed to be strings. The fast, correct way to concatenate a
1210 sequence of strings is by calling ``''.join(sequence)``. Note that
1211 ``sum(range(n), m)`` is equivalent to ``reduce(operator.add, range(n), m)``
1212 To add floating point values with extended precision, see :func:`math.fsum`\.
1214 .. versionadded:: 2.3
1217 .. function:: super(type[, object-or-type])
1219 Return a proxy object that delegates method calls to a parent or sibling
1220 class of *type*. This is useful for accessing inherited methods that have
1221 been overridden in a class. The search order is same as that used by
1222 :func:`getattr` except that the *type* itself is skipped.
1224 The :attr:`__mro__` attribute of the *type* lists the method resolution
1225 search order used by both :func:`getattr` and :func:`super`. The attribute
1226 is dynamic and can change whenever the inheritance hierarchy is updated.
1228 If the second argument is omitted, the super object returned is unbound. If
1229 the second argument is an object, ``isinstance(obj, type)`` must be true. If
1230 the second argument is a type, ``issubclass(type2, type)`` must be true (this
1231 is useful for classmethods).
1234 :func:`super` only works for :term:`new-style class`\es.
1236 There are two typical use cases for *super*. In a class hierarchy with
1237 single inheritance, *super* can be used to refer to parent classes without
1238 naming them explicitly, thus making the code more maintainable. This use
1239 closely parallels the use of *super* in other programming languages.
1241 The second use case is to support cooperative multiple inheritance in a
1242 dynamic execution environment. This use case is unique to Python and is
1243 not found in statically compiled languages or languages that only support
1244 single inheritance. This makes it possible to implement "diamond diagrams"
1245 where multiple base classes implement the same method. Good design dictates
1246 that this method have the same calling signature in every case (because the
1247 order of calls is determined at runtime, because that order adapts
1248 to changes in the class hierarchy, and because that order can include
1249 sibling classes that are unknown prior to runtime).
1251 For both use cases, a typical superclass call looks like this::
1254 def method(self, arg):
1255 super(C, self).method(arg)
1257 Note that :func:`super` is implemented as part of the binding process for
1258 explicit dotted attribute lookups such as ``super().__getitem__(name)``.
1259 It does so by implementing its own :meth:`__getattribute__` method for searching
1260 classes in a predictable order that supports cooperative multiple inheritance.
1261 Accordingly, :func:`super` is undefined for implicit lookups using statements or
1262 operators such as ``super()[name]``.
1264 Also note that :func:`super` is not limited to use inside methods. The two
1265 argument form specifies the arguments exactly and makes the appropriate
1268 .. versionadded:: 2.2
1271 .. function:: tuple([iterable])
1273 Return a tuple whose items are the same and in the same order as *iterable*'s
1274 items. *iterable* may be a sequence, a container that supports iteration, or an
1275 iterator object. If *iterable* is already a tuple, it is returned unchanged.
1276 For instance, ``tuple('abc')`` returns ``('a', 'b', 'c')`` and ``tuple([1, 2,
1277 3])`` returns ``(1, 2, 3)``. If no argument is given, returns a new empty
1280 :class:`tuple` is an immutable sequence type, as documented in
1281 :ref:`typesseq`. For other containers see the built in :class:`dict`,
1282 :class:`list`, and :class:`set` classes, and the :mod:`collections` module.
1285 .. function:: type(object)
1287 .. index:: object: type
1289 Return the type of an *object*. The return value is a type object. The
1290 :func:`isinstance` built-in function is recommended for testing the type of an
1293 With three arguments, :func:`type` functions as a constructor as detailed below.
1296 .. function:: type(name, bases, dict)
1299 Return a new type object. This is essentially a dynamic form of the
1300 :keyword:`class` statement. The *name* string is the class name and becomes the
1301 :attr:`__name__` attribute; the *bases* tuple itemizes the base classes and
1302 becomes the :attr:`__bases__` attribute; and the *dict* dictionary is the
1303 namespace containing definitions for class body and becomes the :attr:`__dict__`
1304 attribute. For example, the following two statements create identical
1305 :class:`type` objects:
1307 >>> class X(object):
1310 >>> X = type('X', (object,), dict(a=1))
1312 .. versionadded:: 2.2
1315 .. function:: unichr(i)
1317 Return the Unicode string of one character whose Unicode code is the integer
1318 *i*. For example, ``unichr(97)`` returns the string ``u'a'``. This is the
1319 inverse of :func:`ord` for Unicode strings. The valid range for the argument
1320 depends how Python was configured -- it may be either UCS2 [0..0xFFFF] or UCS4
1321 [0..0x10FFFF]. :exc:`ValueError` is raised otherwise. For ASCII and 8-bit
1322 strings see :func:`chr`.
1324 .. versionadded:: 2.0
1327 .. function:: unicode([object[, encoding [, errors]]])
1329 Return the Unicode string version of *object* using one of the following modes:
1331 If *encoding* and/or *errors* are given, ``unicode()`` will decode the object
1332 which can either be an 8-bit string or a character buffer using the codec for
1333 *encoding*. The *encoding* parameter is a string giving the name of an encoding;
1334 if the encoding is not known, :exc:`LookupError` is raised. Error handling is
1335 done according to *errors*; this specifies the treatment of characters which are
1336 invalid in the input encoding. If *errors* is ``'strict'`` (the default), a
1337 :exc:`ValueError` is raised on errors, while a value of ``'ignore'`` causes
1338 errors to be silently ignored, and a value of ``'replace'`` causes the official
1339 Unicode replacement character, ``U+FFFD``, to be used to replace input
1340 characters which cannot be decoded. See also the :mod:`codecs` module.
1342 If no optional parameters are given, ``unicode()`` will mimic the behaviour of
1343 ``str()`` except that it returns Unicode strings instead of 8-bit strings. More
1344 precisely, if *object* is a Unicode string or subclass it will return that
1345 Unicode string without any additional decoding applied.
1347 For objects which provide a :meth:`__unicode__` method, it will call this method
1348 without arguments to create a Unicode string. For all other objects, the 8-bit
1349 string version or representation is requested and then converted to a Unicode
1350 string using the codec for the default encoding in ``'strict'`` mode.
1352 For more information on Unicode strings see :ref:`typesseq` which describes
1353 sequence functionality (Unicode strings are sequences), and also the
1354 string-specific methods described in the :ref:`string-methods` section. To
1355 output formatted strings use template strings or the ``%`` operator described
1356 in the :ref:`string-formatting` section. In addition see the
1357 :ref:`stringservices` section. See also :func:`str`.
1359 .. versionadded:: 2.0
1361 .. versionchanged:: 2.2
1362 Support for :meth:`__unicode__` added.
1365 .. function:: vars([object])
1367 Without an argument, act like :func:`locals`.
1369 With a module, class or class instance object as argument (or anything else that
1370 has a :attr:`__dict__` attribute), return that attribute.
1374 The returned dictionary should not be modified:
1375 the effects on the corresponding symbol table are undefined. [#]_
1378 .. function:: xrange([start,] stop[, step])
1380 This function is very similar to :func:`range`, but returns an "xrange object"
1381 instead of a list. This is an opaque sequence type which yields the same values
1382 as the corresponding list, without actually storing them all simultaneously.
1383 The advantage of :func:`xrange` over :func:`range` is minimal (since
1384 :func:`xrange` still has to create the values when asked for them) except when a
1385 very large range is used on a memory-starved machine or when all of the range's
1386 elements are never used (such as when the loop is usually terminated with
1391 :func:`xrange` is intended to be simple and fast. Implementations may
1392 impose restrictions to achieve this. The C implementation of Python
1393 restricts all arguments to native C longs ("short" Python integers), and
1394 also requires that the number of elements fit in a native C long. If a
1395 larger range is needed, an alternate version can be crafted using the
1396 :mod:`itertools` module: ``islice(count(start, step),
1397 (stop-start+step-1)//step)``.
1400 .. function:: zip([iterable, ...])
1402 This function returns a list of tuples, where the *i*-th tuple contains the
1403 *i*-th element from each of the argument sequences or iterables. The returned
1404 list is truncated in length to the length of the shortest argument sequence.
1405 When there are multiple arguments which are all of the same length, :func:`zip`
1406 is similar to :func:`map` with an initial argument of ``None``. With a single
1407 sequence argument, it returns a list of 1-tuples. With no arguments, it returns
1410 The left-to-right evaluation order of the iterables is guaranteed. This
1411 makes possible an idiom for clustering a data series into n-length groups
1412 using ``zip(*[iter(s)]*n)``.
1414 :func:`zip` in conjunction with the ``*`` operator can be used to unzip a
1419 >>> zipped = zip(x, y)
1421 [(1, 4), (2, 5), (3, 6)]
1422 >>> x2, y2 = zip(*zipped)
1423 >>> x == list(x2) and y == list(y2)
1426 .. versionadded:: 2.0
1428 .. versionchanged:: 2.4
1429 Formerly, :func:`zip` required at least one argument and ``zip()`` raised a
1430 :exc:`TypeError` instead of returning an empty list.
1433 .. function:: __import__(name[, globals[, locals[, fromlist[, level]]]])
1441 This is an advanced function that is not needed in everyday Python
1444 This function is invoked by the :keyword:`import` statement. It can be
1445 replaced (by importing the :mod:`builtins` module and assigning to
1446 ``builtins.__import__``) in order to change semantics of the
1447 :keyword:`import` statement, but nowadays it is usually simpler to use import
1448 hooks (see :pep:`302`). Direct use of :func:`__import__` is rare, except in
1449 cases where you want to import a module whose name is only known at runtime.
1451 The function imports the module *name*, potentially using the given *globals*
1452 and *locals* to determine how to interpret the name in a package context.
1453 The *fromlist* gives the names of objects or submodules that should be
1454 imported from the module given by *name*. The standard implementation does
1455 not use its *locals* argument at all, and uses its *globals* only to
1456 determine the package context of the :keyword:`import` statement.
1458 *level* specifies whether to use absolute or relative imports. The default
1459 is ``-1`` which indicates both absolute and relative imports will be
1460 attempted. ``0`` means only perform absolute imports. Positive values for
1461 *level* indicate the number of parent directories to search relative to the
1462 directory of the module calling :func:`__import__`.
1464 When the *name* variable is of the form ``package.module``, normally, the
1465 top-level package (the name up till the first dot) is returned, *not* the
1466 module named by *name*. However, when a non-empty *fromlist* argument is
1467 given, the module named by *name* is returned.
1469 For example, the statement ``import spam`` results in bytecode resembling the
1472 spam = __import__('spam', globals(), locals(), [], -1)
1474 The statement ``import spam.ham`` results in this call::
1476 spam = __import__('spam.ham', globals(), locals(), [], -1)
1478 Note how :func:`__import__` returns the toplevel module here because this is
1479 the object that is bound to a name by the :keyword:`import` statement.
1481 On the other hand, the statement ``from spam.ham import eggs, sausage as
1482 saus`` results in ::
1484 _temp = __import__('spam.ham', globals(), locals(), ['eggs', 'sausage'], -1)
1486 saus = _temp.sausage
1488 Here, the ``spam.ham`` module is returned from :func:`__import__`. From this
1489 object, the names to import are retrieved and assigned to their respective
1492 If you simply want to import a module (potentially within a package) by name,
1493 you can call :func:`__import__` and then look it up in :data:`sys.modules`::
1496 >>> name = 'foo.bar.baz'
1497 >>> __import__(name)
1498 <module 'foo' from ...>
1499 >>> baz = sys.modules[name]
1501 <module 'foo.bar.baz' from ...>
1503 .. versionchanged:: 2.5
1504 The level parameter was added.
1506 .. versionchanged:: 2.5
1507 Keyword support for parameters was added.
1509 .. ---------------------------------------------------------------------------
1512 .. _non-essential-built-in-funcs:
1514 Non-essential Built-in Functions
1515 ================================
1517 There are several built-in functions that are no longer essential to learn, know
1518 or use in modern Python programming. They have been kept here to maintain
1519 backwards compatibility with programs written for older versions of Python.
1521 Python programmers, trainers, students and book writers should feel free to
1522 bypass these functions without concerns about missing something important.
1525 .. function:: apply(function, args[, keywords])
1527 The *function* argument must be a callable object (a user-defined or built-in
1528 function or method, or a class object) and the *args* argument must be a
1529 sequence. The *function* is called with *args* as the argument list; the number
1530 of arguments is the length of the tuple. If the optional *keywords* argument is
1531 present, it must be a dictionary whose keys are strings. It specifies keyword
1532 arguments to be added to the end of the argument list. Calling :func:`apply` is
1533 different from just calling ``function(args)``, since in that case there is
1534 always exactly one argument. The use of :func:`apply` is equivalent to
1535 ``function(*args, **keywords)``.
1538 Use the extended call syntax with ``*args`` and ``**keywords`` instead.
1541 .. function:: buffer(object[, offset[, size]])
1543 The *object* argument must be an object that supports the buffer call interface
1544 (such as strings, arrays, and buffers). A new buffer object will be created
1545 which references the *object* argument. The buffer object will be a slice from
1546 the beginning of *object* (or from the specified *offset*). The slice will
1547 extend to the end of *object* (or will have a length given by the *size*
1551 .. function:: coerce(x, y)
1553 Return a tuple consisting of the two numeric arguments converted to a common
1554 type, using the same rules as used by arithmetic operations. If coercion is not
1555 possible, raise :exc:`TypeError`.
1558 .. function:: intern(string)
1560 Enter *string* in the table of "interned" strings and return the interned string
1561 -- which is *string* itself or a copy. Interning strings is useful to gain a
1562 little performance on dictionary lookup -- if the keys in a dictionary are
1563 interned, and the lookup key is interned, the key comparisons (after hashing)
1564 can be done by a pointer compare instead of a string compare. Normally, the
1565 names used in Python programs are automatically interned, and the dictionaries
1566 used to hold module, class or instance attributes have interned keys.
1568 .. versionchanged:: 2.3
1569 Interned strings are not immortal (like they used to be in Python 2.2 and
1570 before); you must keep a reference to the return value of :func:`intern` around
1573 .. rubric:: Footnotes
1575 .. [#] It is used relatively rarely so does not warrant being made into a statement.
1577 .. [#] Specifying a buffer size currently has no effect on systems that don't have
1578 :cfunc:`setvbuf`. The interface to specify the buffer size is not done using a
1579 method that calls :cfunc:`setvbuf`, because that may dump core when called after
1580 any I/O has been performed, and there's no reliable way to determine whether
1583 .. [#] In the current implementation, local variable bindings cannot normally be
1584 affected this way, but variables retrieved from other scopes (such as modules)
1585 can be. This may change.