1 2 .. _built-in-funcs: 3 4 Built-in Functions 5 ================== 6 7 The Python interpreter has a number of functions built into it that are always 8 available. They are listed here in alphabetical order. 9 10 =================== ================= ================== ================= ==================== 11 .. .. Built-in Functions .. .. 12 =================== ================= ================== ================= ==================== 13 :func:`abs` :func:`divmod` :func:`input` :func:`open` :func:`staticmethod` 14 :func:`all` :func:`enumerate` :func:`int` :func:`ord` :func:`str` 15 :func:`any` :func:`eval` :func:`isinstance` :func:`pow` :func:`sum` 16 :func:`basestring` :func:`execfile` :func:`issubclass` :func:`print` :func:`super` 17 :func:`bin` :func:`file` :func:`iter` :func:`property` :func:`tuple` 18 :func:`bool` :func:`filter` :func:`len` :func:`range` :func:`type` 19 :func:`bytearray` :func:`float` |func-list|_ :func:`raw_input` :func:`unichr` 20 :func:`callable` :func:`format` :func:`locals` :func:`reduce` :func:`unicode` 21 :func:`chr` |func-frozenset|_ :func:`long` :func:`reload` :func:`vars` 22 :func:`classmethod` :func:`getattr` :func:`map` |func-repr|_ :func:`xrange` 23 :func:`cmp` :func:`globals` :func:`max` :func:`reversed` :func:`zip` 24 :func:`compile` :func:`hasattr` |func-memoryview|_ :func:`round` :func:`__import__` 25 :func:`complex` :func:`hash` :func:`min` |func-set|_ .. 26 :func:`delattr` :func:`help` :func:`next` :func:`setattr` .. 27 |func-dict|_ :func:`hex` :func:`object` :func:`slice` .. 28 :func:`dir` :func:`id` :func:`oct` :func:`sorted` .. 29 =================== ================= ================== ================= ==================== 30 31 In addition, there are other four built-in functions that are no longer 32 considered essential: :func:`apply`, :func:`buffer`, :func:`coerce`, and 33 :func:`intern`. They are documented in the :ref:`non-essential-built-in-funcs` 34 section. 35 36 .. using :func:`dict` would create a link to another page, so local targets are 37 used, with replacement texts to make the output in the table consistent 38 39 .. |func-dict| replace:: ``dict()`` 40 .. |func-frozenset| replace:: ``frozenset()`` 41 .. |func-list| replace:: ``list()`` 42 .. |func-memoryview| replace:: ``memoryview()`` 43 .. |func-repr| replace:: ``repr()`` 44 .. |func-set| replace:: ``set()`` 45 46 47 .. function:: abs(x) 48 49 Return the absolute value of a number. The argument may be a plain or long 50 integer or a floating point number. If the argument is a complex number, its 51 magnitude is returned. 52 53 54 .. function:: all(iterable) 55 56 Return ``True`` if all elements of the *iterable* are true (or if the iterable 57 is empty). Equivalent to:: 58 59 def all(iterable): 60 for element in iterable: 61 if not element: 62 return False 63 return True 64 65 .. versionadded:: 2.5 66 67 68 .. function:: any(iterable) 69 70 Return ``True`` if any element of the *iterable* is true. If the iterable 71 is empty, return ``False``. Equivalent to:: 72 73 def any(iterable): 74 for element in iterable: 75 if element: 76 return True 77 return False 78 79 .. versionadded:: 2.5 80 81 82 .. function:: basestring() 83 84 This abstract type is the superclass for :class:`str` and :class:`unicode`. It 85 cannot be called or instantiated, but it can be used to test whether an object 86 is an instance of :class:`str` or :class:`unicode`. ``isinstance(obj, 87 basestring)`` is equivalent to ``isinstance(obj, (str, unicode))``. 88 89 .. versionadded:: 2.3 90 91 92 .. function:: bin(x) 93 94 Convert an integer number to a binary string. The result is a valid Python 95 expression. If *x* is not a Python :class:`int` object, it has to define an 96 :meth:`__index__` method that returns an integer. 97 98 .. versionadded:: 2.6 99 100 101 .. class:: bool([x]) 102 103 Return a Boolean value, i.e. one of ``True`` or ``False``. *x* is converted 104 using the standard truth testing procedure. If *x* is false or omitted, this 105 returns :const:`False`; otherwise it returns :const:`True`. :class:`bool` is 106 also a class, which is a subclass of :class:`int`. Class :class:`bool` cannot 107 be subclassed further. Its only instances are :const:`False` and 108 :const:`True`. 109 110 .. index:: pair: Boolean; type 111 112 .. versionadded:: 2.2.1 113 114 .. versionchanged:: 2.3 115 If no argument is given, this function returns :const:`False`. 116 117 118 .. class:: bytearray([source[, encoding[, errors]]]) 119 120 Return a new array of bytes. The :class:`bytearray` class is a mutable 121 sequence of integers in the range 0 <= x < 256. It has most of the usual 122 methods of mutable sequences, described in :ref:`typesseq-mutable`, as well 123 as most methods that the :class:`str` type has, see :ref:`string-methods`. 124 125 The optional *source* parameter can be used to initialize the array in a few 126 different ways: 127 128 * If it is *unicode*, you must also give the *encoding* (and optionally, 129 *errors*) parameters; :func:`bytearray` then converts the unicode to 130 bytes using :meth:`unicode.encode`. 131 132 * If it is an *integer*, the array will have that size and will be 133 initialized with null bytes. 134 135 * If it is an object conforming to the *buffer* interface, a read-only buffer 136 of the object will be used to initialize the bytes array. 137 138 * If it is an *iterable*, it must be an iterable of integers in the range 139 ``0 <= x < 256``, which are used as the initial contents of the array. 140 141 Without an argument, an array of size 0 is created. 142 143 .. versionadded:: 2.6 144 145 146 .. function:: callable(object) 147 148 Return :const:`True` if the *object* argument appears callable, 149 :const:`False` if not. If this 150 returns true, it is still possible that a call fails, but if it is false, 151 calling *object* will never succeed. Note that classes are callable (calling a 152 class returns a new instance); class instances are callable if they have a 153 :meth:`__call__` method. 154 155 156 .. function:: chr(i) 157 158 Return a string of one character whose ASCII code is the integer *i*. For 159 example, ``chr(97)`` returns the string ``'a'``. This is the inverse of 160 :func:`ord`. The argument must be in the range [0..255], inclusive; 161 :exc:`ValueError` will be raised if *i* is outside that range. See 162 also :func:`unichr`. 163 164 165 .. function:: classmethod(function) 166 167 Return a class method for *function*. 168 169 A class method receives the class as implicit first argument, just like an 170 instance method receives the instance. To declare a class method, use this 171 idiom:: 172 173 class C(object): 174 @classmethod 175 def f(cls, arg1, arg2, ...): 176 ... 177 178 The ``@classmethod`` form is a function :term:`decorator` -- see the description 179 of function definitions in :ref:`function` for details. 180 181 It can be called either on the class (such as ``C.f()``) or on an instance (such 182 as ``C().f()``). The instance is ignored except for its class. If a class 183 method is called for a derived class, the derived class object is passed as the 184 implied first argument. 185 186 Class methods are different than C++ or Java static methods. If you want those, 187 see :func:`staticmethod` in this section. 188 189 For more information on class methods, consult the documentation on the standard 190 type hierarchy in :ref:`types`. 191 192 .. versionadded:: 2.2 193 194 .. versionchanged:: 2.4 195 Function decorator syntax added. 196 197 198 .. function:: cmp(x, y) 199 200 Compare the two objects *x* and *y* and return an integer according to the 201 outcome. The return value is negative if ``x < y``, zero if ``x == y`` and 202 strictly positive if ``x > y``. 203 204 205 .. function:: compile(source, filename, mode[, flags[, dont_inherit]]) 206 207 Compile the *source* into a code or AST object. Code objects can be executed 208 by an :keyword:`exec` statement or evaluated by a call to :func:`eval`. 209 *source* can either be a Unicode string, a *Latin-1* encoded string or an 210 AST object. 211 Refer to the :mod:`ast` module documentation for information on how to work 212 with AST objects. 213 214 The *filename* argument should give the file from which the code was read; 215 pass some recognizable value if it wasn't read from a file (``'<string>'`` is 216 commonly used). 217 218 The *mode* argument specifies what kind of code must be compiled; it can be 219 ``'exec'`` if *source* consists of a sequence of statements, ``'eval'`` if it 220 consists of a single expression, or ``'single'`` if it consists of a single 221 interactive statement (in the latter case, expression statements that 222 evaluate to something other than ``None`` will be printed). 223 224 The optional arguments *flags* and *dont_inherit* control which future 225 statements (see :pep:`236`) affect the compilation of *source*. If neither 226 is present (or both are zero) the code is compiled with those future 227 statements that are in effect in the code that is calling :func:`compile`. If the 228 *flags* argument is given and *dont_inherit* is not (or is zero) then the 229 future statements specified by the *flags* argument are used in addition to 230 those that would be used anyway. If *dont_inherit* is a non-zero integer then 231 the *flags* argument is it -- the future statements in effect around the call 232 to compile are ignored. 233 234 Future statements are specified by bits which can be bitwise ORed together to 235 specify multiple statements. The bitfield required to specify a given feature 236 can be found as the :attr:`~__future__._Feature.compiler_flag` attribute on 237 the :class:`~__future__._Feature` instance in the :mod:`__future__` module. 238 239 This function raises :exc:`SyntaxError` if the compiled source is invalid, 240 and :exc:`TypeError` if the source contains null bytes. 241 242 If you want to parse Python code into its AST representation, see 243 :func:`ast.parse`. 244 245 .. note:: 246 247 When compiling a string with multi-line code in ``'single'`` or 248 ``'eval'`` mode, input must be terminated by at least one newline 249 character. This is to facilitate detection of incomplete and complete 250 statements in the :mod:`code` module. 251 252 .. versionchanged:: 2.3 253 The *flags* and *dont_inherit* arguments were added. 254 255 .. versionchanged:: 2.6 256 Support for compiling AST objects. 257 258 .. versionchanged:: 2.7 259 Allowed use of Windows and Mac newlines. Also input in ``'exec'`` mode 260 does not have to end in a newline anymore. 261 262 263 .. class:: complex([real[, imag]]) 264 265 Return a complex number with the value *real* + *imag*\*1j or convert a string or 266 number to a complex number. If the first parameter is a string, it will be 267 interpreted as a complex number and the function must be called without a second 268 parameter. The second parameter can never be a string. Each argument may be any 269 numeric type (including complex). If *imag* is omitted, it defaults to zero and 270 the function serves as a numeric conversion function like :func:`int`, 271 :func:`long` and :func:`float`. If both arguments are omitted, returns ``0j``. 272 273 .. note:: 274 275 When converting from a string, the string must not contain whitespace 276 around the central ``+`` or ``-`` operator. For example, 277 ``complex('1+2j')`` is fine, but ``complex('1 + 2j')`` raises 278 :exc:`ValueError`. 279 280 The complex type is described in :ref:`typesnumeric`. 281 282 283 .. function:: delattr(object, name) 284 285 This is a relative of :func:`setattr`. The arguments are an object and a 286 string. The string must be the name of one of the object's attributes. The 287 function deletes the named attribute, provided the object allows it. For 288 example, ``delattr(x, 'foobar')`` is equivalent to ``del x.foobar``. 289 290 291 .. _func-dict: 292 .. class:: dict(**kwarg) 293 dict(mapping, **kwarg) 294 dict(iterable, **kwarg) 295 :noindex: 296 297 Create a new dictionary. The :class:`dict` object is the dictionary class. 298 See :class:`dict` and :ref:`typesmapping` for documentation about this class. 299 300 For other containers see the built-in :class:`list`, :class:`set`, and 301 :class:`tuple` classes, as well as the :mod:`collections` module. 302 303 304 .. function:: dir([object]) 305 306 Without arguments, return the list of names in the current local scope. With an 307 argument, attempt to return a list of valid attributes for that object. 308 309 If the object has a method named :meth:`__dir__`, this method will be called and 310 must return the list of attributes. This allows objects that implement a custom 311 :func:`__getattr__` or :func:`__getattribute__` function to customize the way 312 :func:`dir` reports their attributes. 313 314 If the object does not provide :meth:`__dir__`, the function tries its best to 315 gather information from the object's :attr:`~object.__dict__` attribute, if defined, and 316 from its type object. The resulting list is not necessarily complete, and may 317 be inaccurate when the object has a custom :func:`__getattr__`. 318 319 The default :func:`dir` mechanism behaves differently with different types of 320 objects, as it attempts to produce the most relevant, rather than complete, 321 information: 322 323 * If the object is a module object, the list contains the names of the module's 324 attributes. 325 326 * If the object is a type or class object, the list contains the names of its 327 attributes, and recursively of the attributes of its bases. 328 329 * Otherwise, the list contains the object's attributes' names, the names of its 330 class's attributes, and recursively of the attributes of its class's base 331 classes. 332 333 The resulting list is sorted alphabetically. For example: 334 335 >>> import struct 336 >>> dir() # show the names in the module namespace 337 ['__builtins__', '__doc__', '__name__', 'struct'] 338 >>> dir(struct) # show the names in the struct module 339 ['Struct', '__builtins__', '__doc__', '__file__', '__name__', 340 '__package__', '_clearcache', 'calcsize', 'error', 'pack', 'pack_into', 341 'unpack', 'unpack_from'] 342 >>> class Shape(object): 343 def __dir__(self): 344 return ['area', 'perimeter', 'location'] 345 >>> s = Shape() 346 >>> dir(s) 347 ['area', 'perimeter', 'location'] 348 349 .. note:: 350 351 Because :func:`dir` is supplied primarily as a convenience for use at an 352 interactive prompt, it tries to supply an interesting set of names more than it 353 tries to supply a rigorously or consistently defined set of names, and its 354 detailed behavior may change across releases. For example, metaclass attributes 355 are not in the result list when the argument is a class. 356 357 358 .. function:: divmod(a, b) 359 360 Take two (non complex) numbers as arguments and return a pair of numbers 361 consisting of their quotient and remainder when using long division. With mixed 362 operand types, the rules for binary arithmetic operators apply. For plain and 363 long integers, the result is the same as ``(a // b, a % b)``. For floating point 364 numbers the result is ``(q, a % b)``, where *q* is usually ``math.floor(a / b)`` 365 but may be 1 less than that. In any case ``q * b + a % b`` is very close to 366 *a*, if ``a % b`` is non-zero it has the same sign as *b*, and ``0 <= abs(a % b) 367 < abs(b)``. 368 369 .. versionchanged:: 2.3 370 Using :func:`divmod` with complex numbers is deprecated. 371 372 373 .. function:: enumerate(sequence, start=0) 374 375 Return an enumerate object. *sequence* must be a sequence, an 376 :term:`iterator`, or some other object which supports iteration. The 377 :meth:`!next` method of the iterator returned by :func:`enumerate` returns a 378 tuple containing a count (from *start* which defaults to 0) and the 379 values obtained from iterating over *sequence*:: 380 381 >>> seasons = ['Spring', 'Summer', 'Fall', 'Winter'] 382 >>> list(enumerate(seasons)) 383 [(0, 'Spring'), (1, 'Summer'), (2, 'Fall'), (3, 'Winter')] 384 >>> list(enumerate(seasons, start=1)) 385 [(1, 'Spring'), (2, 'Summer'), (3, 'Fall'), (4, 'Winter')] 386 387 Equivalent to:: 388 389 def enumerate(sequence, start=0): 390 n = start 391 for elem in sequence: 392 yield n, elem 393 n += 1 394 395 .. versionadded:: 2.3 396 .. versionchanged:: 2.6 397 The *start* parameter was added. 398 399 400 .. function:: eval(expression[, globals[, locals]]) 401 402 The arguments are a Unicode or *Latin-1* encoded string and optional 403 globals and locals. If provided, *globals* must be a dictionary. 404 If provided, *locals* can be any mapping object. 405 406 .. versionchanged:: 2.4 407 formerly *locals* was required to be a dictionary. 408 409 The *expression* argument is parsed and evaluated as a Python expression 410 (technically speaking, a condition list) using the *globals* and *locals* 411 dictionaries as global and local namespace. If the *globals* dictionary is 412 present and lacks '__builtins__', the current globals are copied into *globals* 413 before *expression* is parsed. This means that *expression* normally has full 414 access to the standard :mod:`__builtin__` module and restricted environments are 415 propagated. If the *locals* dictionary is omitted it defaults to the *globals* 416 dictionary. If both dictionaries are omitted, the expression is executed in the 417 environment where :func:`eval` is called. The return value is the result of 418 the evaluated expression. Syntax errors are reported as exceptions. Example: 419 420 >>> x = 1 421 >>> print eval('x+1') 422 2 423 424 This function can also be used to execute arbitrary code objects (such as 425 those created by :func:`compile`). In this case pass a code object instead 426 of a string. If the code object has been compiled with ``'exec'`` as the 427 *mode* argument, :func:`eval`\'s return value will be ``None``. 428 429 Hints: dynamic execution of statements is supported by the :keyword:`exec` 430 statement. Execution of statements from a file is supported by the 431 :func:`execfile` function. The :func:`globals` and :func:`locals` functions 432 returns the current global and local dictionary, respectively, which may be 433 useful to pass around for use by :func:`eval` or :func:`execfile`. 434 435 See :func:`ast.literal_eval` for a function that can safely evaluate strings 436 with expressions containing only literals. 437 438 439 .. function:: execfile(filename[, globals[, locals]]) 440 441 This function is similar to the :keyword:`exec` statement, but parses a file 442 instead of a string. It is different from the :keyword:`import` statement in 443 that it does not use the module administration --- it reads the file 444 unconditionally and does not create a new module. [#]_ 445 446 The arguments are a file name and two optional dictionaries. The file is parsed 447 and evaluated as a sequence of Python statements (similarly to a module) using 448 the *globals* and *locals* dictionaries as global and local namespace. If 449 provided, *locals* can be any mapping object. Remember that at module level, 450 globals and locals are the same dictionary. If two separate objects are 451 passed as *globals* and *locals*, the code will be executed as if it were 452 embedded in a class definition. 453 454 .. versionchanged:: 2.4 455 formerly *locals* was required to be a dictionary. 456 457 If the *locals* dictionary is omitted it defaults to the *globals* dictionary. 458 If both dictionaries are omitted, the expression is executed in the environment 459 where :func:`execfile` is called. The return value is ``None``. 460 461 .. note:: 462 463 The default *locals* act as described for function :func:`locals` below: 464 modifications to the default *locals* dictionary should not be attempted. Pass 465 an explicit *locals* dictionary if you need to see effects of the code on 466 *locals* after function :func:`execfile` returns. :func:`execfile` cannot be 467 used reliably to modify a function's locals. 468 469 470 .. function:: file(name[, mode[, buffering]]) 471 472 Constructor function for the :class:`file` type, described further in section 473 :ref:`bltin-file-objects`. The constructor's arguments are the same as those 474 of the :func:`open` built-in function described below. 475 476 When opening a file, it's preferable to use :func:`open` instead of invoking 477 this constructor directly. :class:`file` is more suited to type testing (for 478 example, writing ``isinstance(f, file)``). 479 480 .. versionadded:: 2.2 481 482 483 .. function:: filter(function, iterable) 484 485 Construct a list from those elements of *iterable* for which *function* returns 486 true. *iterable* may be either a sequence, a container which supports 487 iteration, or an iterator. If *iterable* is a string or a tuple, the result 488 also has that type; otherwise it is always a list. If *function* is ``None``, 489 the identity function is assumed, that is, all elements of *iterable* that are 490 false are removed. 491 492 Note that ``filter(function, iterable)`` is equivalent to ``[item for item in 493 iterable if function(item)]`` if function is not ``None`` and ``[item for item 494 in iterable if item]`` if function is ``None``. 495 496 See :func:`itertools.ifilter` and :func:`itertools.ifilterfalse` for iterator 497 versions of this function, including a variation that filters for elements 498 where the *function* returns false. 499 500 501 .. class:: float([x]) 502 503 Return a floating point number constructed from a number or string *x*. 504 505 If the argument is a string, it 506 must contain a possibly signed decimal or floating point number, possibly 507 embedded in whitespace. The argument may also be [+|-]nan or [+|-]inf. 508 Otherwise, the argument may be a plain or long integer 509 or a floating point number, and a floating point number with the same value 510 (within Python's floating point precision) is returned. If no argument is 511 given, returns ``0.0``. 512 513 .. note:: 514 515 .. index:: 516 single: NaN 517 single: Infinity 518 519 When passing in a string, values for NaN and Infinity may be returned, depending 520 on the underlying C library. Float accepts the strings nan, inf and -inf for 521 NaN and positive or negative infinity. The case and a leading + are ignored as 522 well as a leading - is ignored for NaN. Float always represents NaN and infinity 523 as nan, inf or -inf. 524 525 The float type is described in :ref:`typesnumeric`. 526 527 528 .. function:: format(value[, format_spec]) 529 530 .. index:: 531 pair: str; format 532 single: __format__ 533 534 Convert a *value* to a "formatted" representation, as controlled by 535 *format_spec*. The interpretation of *format_spec* will depend on the type 536 of the *value* argument, however there is a standard formatting syntax that 537 is used by most built-in types: :ref:`formatspec`. 538 539 .. note:: 540 541 ``format(value, format_spec)`` merely calls 542 ``value.__format__(format_spec)``. 543 544 .. versionadded:: 2.6 545 546 547 .. _func-frozenset: 548 .. class:: frozenset([iterable]) 549 :noindex: 550 551 Return a new :class:`frozenset` object, optionally with elements taken from 552 *iterable*. ``frozenset`` is a built-in class. See :class:`frozenset` and 553 :ref:`types-set` for documentation about this class. 554 555 For other containers see the built-in :class:`set`, :class:`list`, 556 :class:`tuple`, and :class:`dict` classes, as well as the :mod:`collections` 557 module. 558 559 .. versionadded:: 2.4 560 561 562 .. function:: getattr(object, name[, default]) 563 564 Return the value of the named attribute of *object*. *name* must be a string. 565 If the string is the name of one of the object's attributes, the result is the 566 value of that attribute. For example, ``getattr(x, 'foobar')`` is equivalent to 567 ``x.foobar``. If the named attribute does not exist, *default* is returned if 568 provided, otherwise :exc:`AttributeError` is raised. 569 570 571 .. function:: globals() 572 573 Return a dictionary representing the current global symbol table. This is always 574 the dictionary of the current module (inside a function or method, this is the 575 module where it is defined, not the module from which it is called). 576 577 578 .. function:: hasattr(object, name) 579 580 The arguments are an object and a string. The result is ``True`` if the string 581 is the name of one of the object's attributes, ``False`` if not. (This is 582 implemented by calling ``getattr(object, name)`` and seeing whether it raises an 583 exception or not.) 584 585 586 .. function:: hash(object) 587 588 Return the hash value of the object (if it has one). Hash values are integers. 589 They are used to quickly compare dictionary keys during a dictionary lookup. 590 Numeric values that compare equal have the same hash value (even if they are of 591 different types, as is the case for 1 and 1.0). 592 593 594 .. function:: help([object]) 595 596 Invoke the built-in help system. (This function is intended for interactive 597 use.) If no argument is given, the interactive help system starts on the 598 interpreter console. If the argument is a string, then the string is looked up 599 as the name of a module, function, class, method, keyword, or documentation 600 topic, and a help page is printed on the console. If the argument is any other 601 kind of object, a help page on the object is generated. 602 603 This function is added to the built-in namespace by the :mod:`site` module. 604 605 .. versionadded:: 2.2 606 607 608 .. function:: hex(x) 609 610 Convert an integer number (of any size) to a lowercase hexadecimal string 611 prefixed with "0x", for example: 612 613 >>> hex(255) 614 '0xff' 615 >>> hex(-42) 616 '-0x2a' 617 >>> hex(1L) 618 '0x1L' 619 620 If x is not a Python :class:`int` or :class:`long` object, it has to 621 define a __hex__() method that returns a string. 622 623 See also :func:`int` for converting a hexadecimal string to an 624 integer using a base of 16. 625 626 .. note:: 627 628 To obtain a hexadecimal string representation for a float, use the 629 :meth:`float.hex` method. 630 631 .. versionchanged:: 2.4 632 Formerly only returned an unsigned literal. 633 634 635 .. function:: id(object) 636 637 Return the "identity" of an object. This is an integer (or long integer) which 638 is guaranteed to be unique and constant for this object during its lifetime. 639 Two objects with non-overlapping lifetimes may have the same :func:`id` 640 value. 641 642 .. impl-detail:: This is the address of the object in memory. 643 644 645 .. function:: input([prompt]) 646 647 Equivalent to ``eval(raw_input(prompt))``. 648 649 This function does not catch user errors. If the input is not syntactically 650 valid, a :exc:`SyntaxError` will be raised. Other exceptions may be raised if 651 there is an error during evaluation. 652 653 If the :mod:`readline` module was loaded, then :func:`input` will use it to 654 provide elaborate line editing and history features. 655 656 Consider using the :func:`raw_input` function for general input from users. 657 658 659 .. class:: int(x=0) 660 int(x, base=10) 661 662 Return an integer object constructed from a number or string *x*, or return ``0`` if no 663 arguments are given. If *x* is a number, it can be a plain integer, a long 664 integer, or a floating point number. If *x* is floating point, the conversion 665 truncates towards zero. If the argument is outside the integer range, the 666 function returns a long object instead. 667 668 If *x* is not a number or if *base* is given, then *x* must be a string or 669 Unicode object representing an :ref:`integer literal <integers>` in radix 670 *base*. Optionally, the literal can be 671 preceded by ``+`` or ``-`` (with no space in between) and surrounded by 672 whitespace. A base-n literal consists of the digits 0 to n-1, with ``a`` 673 to ``z`` (or ``A`` to ``Z``) having 674 values 10 to 35. The default *base* is 10. The allowed values are 0 and 2--36. 675 Base-2, -8, and -16 literals can be optionally prefixed with ``0b``/``0B``, 676 ``0o``/``0O``/``0``, or ``0x``/``0X``, as with integer literals in code. 677 Base 0 means to interpret the string exactly as an integer literal, so that 678 the actual base is 2, 8, 10, or 16. 679 680 The integer type is described in :ref:`typesnumeric`. 681 682 683 .. function:: isinstance(object, classinfo) 684 685 Return true if the *object* argument is an instance of the *classinfo* argument, 686 or of a (direct, indirect or :term:`virtual <abstract base class>`) subclass 687 thereof. Also return true if *classinfo* 688 is a type object (new-style class) and *object* is an object of that type or of 689 a (direct, indirect or :term:`virtual <abstract base class>`) subclass 690 thereof. If *object* is not a class instance or 691 an object of the given type, the function always returns false. 692 If *classinfo* is a tuple of class or type objects (or recursively, other 693 such tuples), return true if *object* is an instance of any of the classes 694 or types. If *classinfo* is not a class, type, or tuple of classes, types, 695 and such tuples, a :exc:`TypeError` exception is raised. 696 697 .. versionchanged:: 2.2 698 Support for a tuple of type information was added. 699 700 701 .. function:: issubclass(class, classinfo) 702 703 Return true if *class* is a subclass (direct, indirect or :term:`virtual 704 <abstract base class>`) of *classinfo*. A 705 class is considered a subclass of itself. *classinfo* may be a tuple of class 706 objects, in which case every entry in *classinfo* will be checked. In any other 707 case, a :exc:`TypeError` exception is raised. 708 709 .. versionchanged:: 2.3 710 Support for a tuple of type information was added. 711 712 713 .. function:: iter(o[, sentinel]) 714 715 Return an :term:`iterator` object. The first argument is interpreted very differently 716 depending on the presence of the second argument. Without a second argument, *o* 717 must be a collection object which supports the iteration protocol (the 718 :meth:`__iter__` method), or it must support the sequence protocol (the 719 :meth:`__getitem__` method with integer arguments starting at ``0``). If it 720 does not support either of those protocols, :exc:`TypeError` is raised. If the 721 second argument, *sentinel*, is given, then *o* must be a callable object. The 722 iterator created in this case will call *o* with no arguments for each call to 723 its :meth:`~iterator.next` method; if the value returned is equal to *sentinel*, 724 :exc:`StopIteration` will be raised, otherwise the value will be returned. 725 726 One useful application of the second form of :func:`iter` is to read lines of 727 a file until a certain line is reached. The following example reads a file 728 until the :meth:`~io.TextIOBase.readline` method returns an empty string:: 729 730 with open('mydata.txt') as fp: 731 for line in iter(fp.readline, ''): 732 process_line(line) 733 734 .. versionadded:: 2.2 735 736 737 .. function:: len(s) 738 739 Return the length (the number of items) of an object. The argument may be a 740 sequence (such as a string, bytes, tuple, list, or range) or a collection 741 (such as a dictionary, set, or frozen set). 742 743 744 .. _func-list: 745 .. class:: list([iterable]) 746 :noindex: 747 748 Return a list whose items are the same and in the same order as *iterable*'s 749 items. *iterable* may be either a sequence, a container that supports 750 iteration, or an iterator object. If *iterable* is already a list, a copy is 751 made and returned, similar to ``iterable[:]``. For instance, ``list('abc')`` 752 returns ``['a', 'b', 'c']`` and ``list( (1, 2, 3) )`` returns ``[1, 2, 3]``. If 753 no argument is given, returns a new empty list, ``[]``. 754 755 :class:`list` is a mutable sequence type, as documented in 756 :ref:`typesseq`. For other containers see the built in :class:`dict`, 757 :class:`set`, and :class:`tuple` classes, and the :mod:`collections` module. 758 759 760 .. function:: locals() 761 762 Update and return a dictionary representing the current local symbol table. 763 Free variables are returned by :func:`locals` when it is called in function 764 blocks, but not in class blocks. 765 766 .. note:: 767 768 The contents of this dictionary should not be modified; changes may not 769 affect the values of local and free variables used by the interpreter. 770 771 772 .. class:: long(x=0) 773 long(x, base=10) 774 775 Return a long integer object constructed from a string or number *x*. 776 If the argument is a string, it 777 must contain a possibly signed number of arbitrary size, possibly embedded in 778 whitespace. The *base* argument is interpreted in the same way as for 779 :func:`int`, and may only be given when *x* is a string. Otherwise, the argument 780 may be a plain or long integer or a floating point number, and a long integer 781 with the same value is returned. Conversion of floating point numbers to 782 integers truncates (towards zero). If no arguments are given, returns ``0L``. 783 784 The long type is described in :ref:`typesnumeric`. 785 786 787 .. function:: map(function, iterable, ...) 788 789 Apply *function* to every item of *iterable* and return a list of the results. 790 If additional *iterable* arguments are passed, *function* must take that many 791 arguments and is applied to the items from all iterables in parallel. If one 792 iterable is shorter than another it is assumed to be extended with ``None`` 793 items. If *function* is ``None``, the identity function is assumed; if there 794 are multiple arguments, :func:`map` returns a list consisting of tuples 795 containing the corresponding items from all iterables (a kind of transpose 796 operation). The *iterable* arguments may be a sequence or any iterable object; 797 the result is always a list. 798 799 800 .. function:: max(iterable[, key]) 801 max(arg1, arg2, *args[, key]) 802 803 Return the largest item in an iterable or the largest of two or more 804 arguments. 805 806 If one positional argument is provided, *iterable* must be a non-empty 807 iterable (such as a non-empty string, tuple or list). The largest item 808 in the iterable is returned. If two or more positional arguments are 809 provided, the largest of the positional arguments is returned. 810 811 The optional *key* argument specifies a one-argument ordering function like that 812 used for :meth:`list.sort`. The *key* argument, if supplied, must be in keyword 813 form (for example, ``max(a,b,c,key=func)``). 814 815 .. versionchanged:: 2.5 816 Added support for the optional *key* argument. 817 818 .. _func-memoryview: 819 .. function:: memoryview(obj) 820 :noindex: 821 822 Return a "memory view" object created from the given argument. See 823 :ref:`typememoryview` for more information. 824 825 826 .. function:: min(iterable[, key]) 827 min(arg1, arg2, *args[, key]) 828 829 Return the smallest item in an iterable or the smallest of two or more 830 arguments. 831 832 If one positional argument is provided, *iterable* must be a non-empty 833 iterable (such as a non-empty string, tuple or list). The smallest item 834 in the iterable is returned. If two or more positional arguments are 835 provided, the smallest of the positional arguments is returned. 836 837 The optional *key* argument specifies a one-argument ordering function like that 838 used for :meth:`list.sort`. The *key* argument, if supplied, must be in keyword 839 form (for example, ``min(a,b,c,key=func)``). 840 841 .. versionchanged:: 2.5 842 Added support for the optional *key* argument. 843 844 845 .. function:: next(iterator[, default]) 846 847 Retrieve the next item from the *iterator* by calling its 848 :meth:`~iterator.next` method. If *default* is given, it is returned if the 849 iterator is exhausted, otherwise :exc:`StopIteration` is raised. 850 851 .. versionadded:: 2.6 852 853 854 .. class:: object() 855 856 Return a new featureless object. :class:`object` is a base for all new style 857 classes. It has the methods that are common to all instances of new style 858 classes. 859 860 .. versionadded:: 2.2 861 862 .. versionchanged:: 2.3 863 This function does not accept any arguments. Formerly, it accepted arguments but 864 ignored them. 865 866 867 .. function:: oct(x) 868 869 Convert an integer number (of any size) to an octal string. The result is a 870 valid Python expression. 871 872 .. versionchanged:: 2.4 873 Formerly only returned an unsigned literal. 874 875 876 .. function:: open(name[, mode[, buffering]]) 877 878 Open a file, returning an object of the :class:`file` type described in 879 section :ref:`bltin-file-objects`. If the file cannot be opened, 880 :exc:`IOError` is raised. When opening a file, it's preferable to use 881 :func:`open` instead of invoking the :class:`file` constructor directly. 882 883 The first two arguments are the same as for ``stdio``'s :c:func:`fopen`: 884 *name* is the file name to be opened, and *mode* is a string indicating how 885 the file is to be opened. 886 887 The most commonly-used values of *mode* are ``'r'`` for reading, ``'w'`` for 888 writing (truncating the file if it already exists), and ``'a'`` for appending 889 (which on *some* Unix systems means that *all* writes append to the end of the 890 file regardless of the current seek position). If *mode* is omitted, it 891 defaults to ``'r'``. The default is to use text mode, which may convert 892 ``'\n'`` characters to a platform-specific representation on writing and back 893 on reading. Thus, when opening a binary file, you should append ``'b'`` to 894 the *mode* value to open the file in binary mode, which will improve 895 portability. (Appending ``'b'`` is useful even on systems that don't treat 896 binary and text files differently, where it serves as documentation.) See below 897 for more possible values of *mode*. 898 899 .. index:: 900 single: line-buffered I/O 901 single: unbuffered I/O 902 single: buffer size, I/O 903 single: I/O control; buffering 904 905 The optional *buffering* argument specifies the file's desired buffer size: 0 906 means unbuffered, 1 means line buffered, any other positive value means use a 907 buffer of (approximately) that size (in bytes). A negative *buffering* means 908 to use the system default, which is usually line buffered for tty devices and 909 fully buffered for other files. If omitted, the system default is used. [#]_ 910 911 Modes ``'r+'``, ``'w+'`` and ``'a+'`` open the file for updating (reading and writing); 912 note that ``'w+'`` truncates the file. Append ``'b'`` to the mode to open the file in 913 binary mode, on systems that differentiate between binary and text files; on 914 systems that don't have this distinction, adding the ``'b'`` has no effect. 915 916 .. index:: 917 single: universal newlines; open() built-in function 918 919 In addition to the standard :c:func:`fopen` values *mode* may be ``'U'`` or 920 ``'rU'``. Python is usually built with :term:`universal newlines` support; 921 supplying ``'U'`` opens the file as a text file, but lines may be terminated 922 by any of the following: the Unix end-of-line convention ``'\n'``, the 923 Macintosh convention ``'\r'``, or the Windows convention ``'\r\n'``. All of 924 these external representations are seen as ``'\n'`` by the Python program. 925 If Python is built without universal newlines support a *mode* with ``'U'`` 926 is the same as normal text mode. Note that file objects so opened also have 927 an attribute called :attr:`newlines` which has a value of ``None`` (if no 928 newlines have yet been seen), ``'\n'``, ``'\r'``, ``'\r\n'``, or a tuple 929 containing all the newline types seen. 930 931 Python enforces that the mode, after stripping ``'U'``, begins with ``'r'``, 932 ``'w'`` or ``'a'``. 933 934 Python provides many file handling modules including 935 :mod:`fileinput`, :mod:`os`, :mod:`os.path`, :mod:`tempfile`, and 936 :mod:`shutil`. 937 938 .. versionchanged:: 2.5 939 Restriction on first letter of mode string introduced. 940 941 942 .. function:: ord(c) 943 944 Given a string of length one, return an integer representing the Unicode code 945 point of the character when the argument is a unicode object, or the value of 946 the byte when the argument is an 8-bit string. For example, ``ord('a')`` returns 947 the integer ``97``, ``ord(u'\u2020')`` returns ``8224``. This is the inverse of 948 :func:`chr` for 8-bit strings and of :func:`unichr` for unicode objects. If a 949 unicode argument is given and Python was built with UCS2 Unicode, then the 950 character's code point must be in the range [0..65535] inclusive; otherwise the 951 string length is two, and a :exc:`TypeError` will be raised. 952 953 954 .. function:: pow(x, y[, z]) 955 956 Return *x* to the power *y*; if *z* is present, return *x* to the power *y*, 957 modulo *z* (computed more efficiently than ``pow(x, y) % z``). The two-argument 958 form ``pow(x, y)`` is equivalent to using the power operator: ``x**y``. 959 960 The arguments must have numeric types. With mixed operand types, the coercion 961 rules for binary arithmetic operators apply. For int and long int operands, the 962 result has the same type as the operands (after coercion) unless the second 963 argument is negative; in that case, all arguments are converted to float and a 964 float result is delivered. For example, ``10**2`` returns ``100``, but 965 ``10**-2`` returns ``0.01``. (This last feature was added in Python 2.2. In 966 Python 2.1 and before, if both arguments were of integer types and the second 967 argument was negative, an exception was raised.) If the second argument is 968 negative, the third argument must be omitted. If *z* is present, *x* and *y* 969 must be of integer types, and *y* must be non-negative. (This restriction was 970 added in Python 2.2. In Python 2.1 and before, floating 3-argument ``pow()`` 971 returned platform-dependent results depending on floating-point rounding 972 accidents.) 973 974 975 .. function:: print(*objects, sep=' ', end='\\n', file=sys.stdout) 976 977 Print *objects* to the stream *file*, separated by *sep* and followed by 978 *end*. *sep*, *end* and *file*, if present, must be given as keyword 979 arguments. 980 981 All non-keyword arguments are converted to strings like :func:`str` does and 982 written to the stream, separated by *sep* and followed by *end*. Both *sep* 983 and *end* must be strings; they can also be ``None``, which means to use the 984 default values. If no *objects* are given, :func:`print` will just write 985 *end*. 986 987 The *file* argument must be an object with a ``write(string)`` method; if it 988 is not present or ``None``, :data:`sys.stdout` will be used. Output buffering 989 is determined by *file*. Use ``file.flush()`` to ensure, for instance, 990 immediate appearance on a screen. 991 992 .. note:: 993 994 This function is not normally available as a built-in since the name 995 ``print`` is recognized as the :keyword:`print` statement. To disable the 996 statement and use the :func:`print` function, use this future statement at 997 the top of your module:: 998 999 from __future__ import print_function 1000 1001 .. versionadded:: 2.6 1002 1003 1004 .. class:: property([fget[, fset[, fdel[, doc]]]]) 1005 1006 Return a property attribute for :term:`new-style class`\es (classes that 1007 derive from :class:`object`). 1008 1009 *fget* is a function for getting an attribute value. *fset* is a function 1010 for setting an attribute value. *fdel* is a function for deleting an attribute 1011 value. And *doc* creates a docstring for the attribute. 1012 1013 A typical use is to define a managed attribute ``x``:: 1014 1015 class C(object): 1016 def __init__(self): 1017 self._x = None 1018 1019 def getx(self): 1020 return self._x 1021 1022 def setx(self, value): 1023 self._x = value 1024 1025 def delx(self): 1026 del self._x 1027 1028 x = property(getx, setx, delx, "I'm the 'x' property.") 1029 1030 If *c* is an instance of *C*, ``c.x`` will invoke the getter, 1031 ``c.x = value`` will invoke the setter and ``del c.x`` the deleter. 1032 1033 If given, *doc* will be the docstring of the property attribute. Otherwise, the 1034 property will copy *fget*'s docstring (if it exists). This makes it possible to 1035 create read-only properties easily using :func:`property` as a :term:`decorator`:: 1036 1037 class Parrot(object): 1038 def __init__(self): 1039 self._voltage = 100000 1040 1041 @property 1042 def voltage(self): 1043 """Get the current voltage.""" 1044 return self._voltage 1045 1046 The ``@property`` decorator turns the :meth:`voltage` method into a "getter" 1047 for a read-only attribute with the same name, and it sets the docstring for 1048 *voltage* to "Get the current voltage." 1049 1050 A property object has :attr:`~property.getter`, :attr:`~property.setter`, 1051 and :attr:`~property.deleter` methods usable as decorators that create a 1052 copy of the property with the corresponding accessor function set to the 1053 decorated function. This is best explained with an example:: 1054 1055 class C(object): 1056 def __init__(self): 1057 self._x = None 1058 1059 @property 1060 def x(self): 1061 """I'm the 'x' property.""" 1062 return self._x 1063 1064 @x.setter 1065 def x(self, value): 1066 self._x = value 1067 1068 @x.deleter 1069 def x(self): 1070 del self._x 1071 1072 This code is exactly equivalent to the first example. Be sure to give the 1073 additional functions the same name as the original property (``x`` in this 1074 case.) 1075 1076 The returned property object also has the attributes ``fget``, ``fset``, and 1077 ``fdel`` corresponding to the constructor arguments. 1078 1079 .. versionadded:: 2.2 1080 1081 .. versionchanged:: 2.5 1082 Use *fget*'s docstring if no *doc* given. 1083 1084 .. versionchanged:: 2.6 1085 The ``getter``, ``setter``, and ``deleter`` attributes were added. 1086 1087 1088 .. function:: range(stop) 1089 range(start, stop[, step]) 1090 1091 This is a versatile function to create lists containing arithmetic progressions. 1092 It is most often used in :keyword:`for` loops. The arguments must be plain 1093 integers. If the *step* argument is omitted, it defaults to ``1``. If the 1094 *start* argument is omitted, it defaults to ``0``. The full form returns a list 1095 of plain integers ``[start, start + step, start + 2 * step, ...]``. If *step* 1096 is positive, the last element is the largest ``start + i * step`` less than 1097 *stop*; if *step* is negative, the last element is the smallest ``start + i * 1098 step`` greater than *stop*. *step* must not be zero (or else :exc:`ValueError` 1099 is raised). Example: 1100 1101 >>> range(10) 1102 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] 1103 >>> range(1, 11) 1104 [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] 1105 >>> range(0, 30, 5) 1106 [0, 5, 10, 15, 20, 25] 1107 >>> range(0, 10, 3) 1108 [0, 3, 6, 9] 1109 >>> range(0, -10, -1) 1110 [0, -1, -2, -3, -4, -5, -6, -7, -8, -9] 1111 >>> range(0) 1112 [] 1113 >>> range(1, 0) 1114 [] 1115 1116 1117 .. function:: raw_input([prompt]) 1118 1119 If the *prompt* argument is present, it is written to standard output without a 1120 trailing newline. The function then reads a line from input, converts it to a 1121 string (stripping a trailing newline), and returns that. When EOF is read, 1122 :exc:`EOFError` is raised. Example:: 1123 1124 >>> s = raw_input('--> ') 1125 --> Monty Python's Flying Circus 1126 >>> s 1127 "Monty Python's Flying Circus" 1128 1129 If the :mod:`readline` module was loaded, then :func:`raw_input` will use it to 1130 provide elaborate line editing and history features. 1131 1132 1133 .. function:: reduce(function, iterable[, initializer]) 1134 1135 Apply *function* of two arguments cumulatively to the items of *iterable*, from 1136 left to right, so as to reduce the iterable to a single value. For example, 1137 ``reduce(lambda x, y: x+y, [1, 2, 3, 4, 5])`` calculates ``((((1+2)+3)+4)+5)``. 1138 The left argument, *x*, is the accumulated value and the right argument, *y*, is 1139 the update value from the *iterable*. If the optional *initializer* is present, 1140 it is placed before the items of the iterable in the calculation, and serves as 1141 a default when the iterable is empty. If *initializer* is not given and 1142 *iterable* contains only one item, the first item is returned. 1143 Roughly equivalent to:: 1144 1145 def reduce(function, iterable, initializer=None): 1146 it = iter(iterable) 1147 if initializer is None: 1148 try: 1149 initializer = next(it) 1150 except StopIteration: 1151 raise TypeError('reduce() of empty sequence with no initial value') 1152 accum_value = initializer 1153 for x in it: 1154 accum_value = function(accum_value, x) 1155 return accum_value 1156 1157 .. function:: reload(module) 1158 1159 Reload a previously imported *module*. The argument must be a module object, so 1160 it must have been successfully imported before. This is useful if you have 1161 edited the module source file using an external editor and want to try out the 1162 new version without leaving the Python interpreter. The return value is the 1163 module object (the same as the *module* argument). 1164 1165 When ``reload(module)`` is executed: 1166 1167 * Python modules' code is recompiled and the module-level code reexecuted, 1168 defining a new set of objects which are bound to names in the module's 1169 dictionary. The ``init`` function of extension modules is not called a second 1170 time. 1171 1172 * As with all other objects in Python the old objects are only reclaimed after 1173 their reference counts drop to zero. 1174 1175 * The names in the module namespace are updated to point to any new or changed 1176 objects. 1177 1178 * Other references to the old objects (such as names external to the module) are 1179 not rebound to refer to the new objects and must be updated in each namespace 1180 where they occur if that is desired. 1181 1182 There are a number of other caveats: 1183 1184 When a module is reloaded, its dictionary (containing the module's global 1185 variables) is retained. Redefinitions of names will override the old 1186 definitions, so this is generally not a problem. If the new version of a module 1187 does not define a name that was defined by the old version, the old definition 1188 remains. This feature can be used to the module's advantage if it maintains a 1189 global table or cache of objects --- with a :keyword:`try` statement it can test 1190 for the table's presence and skip its initialization if desired:: 1191 1192 try: 1193 cache 1194 except NameError: 1195 cache = {} 1196 1197 It is generally not very useful to reload built-in or dynamically loaded 1198 modules. Reloading :mod:`sys`, :mod:`__main__`, :mod:`builtins` and other 1199 key modules is not recommended. In many cases extension modules are not 1200 designed to be initialized more than once, and may fail in arbitrary ways 1201 when reloaded. 1202 1203 If a module imports objects from another module using :keyword:`from` ... 1204 :keyword:`import` ..., calling :func:`reload` for the other module does not 1205 redefine the objects imported from it --- one way around this is to re-execute 1206 the :keyword:`from` statement, another is to use :keyword:`import` and qualified 1207 names (*module*.*name*) instead. 1208 1209 If a module instantiates instances of a class, reloading the module that defines 1210 the class does not affect the method definitions of the instances --- they 1211 continue to use the old class definition. The same is true for derived classes. 1212 1213 1214 .. _func-repr: 1215 .. function:: repr(object) 1216 1217 Return a string containing a printable representation of an object. This is 1218 the same value yielded by conversions (reverse quotes). It is sometimes 1219 useful to be able to access this operation as an ordinary function. For many 1220 types, this function makes an attempt to return a string that would yield an 1221 object with the same value when passed to :func:`eval`, otherwise the 1222 representation is a string enclosed in angle brackets that contains the name 1223 of the type of the object together with additional information often 1224 including the name and address of the object. A class can control what this 1225 function returns for its instances by defining a :meth:`__repr__` method. 1226 1227 1228 .. function:: reversed(seq) 1229 1230 Return a reverse :term:`iterator`. *seq* must be an object which has 1231 a :meth:`__reversed__` method or supports the sequence protocol (the 1232 :meth:`__len__` method and the :meth:`__getitem__` method with integer 1233 arguments starting at ``0``). 1234 1235 .. versionadded:: 2.4 1236 1237 .. versionchanged:: 2.6 1238 Added the possibility to write a custom :meth:`__reversed__` method. 1239 1240 1241 .. function:: round(number[, ndigits]) 1242 1243 Return the floating point value *number* rounded to *ndigits* digits after 1244 the decimal point. If *ndigits* is omitted, it defaults to zero. The result 1245 is a floating point number. Values are rounded to the closest multiple of 1246 10 to the power minus *ndigits*; if two multiples are equally close, 1247 rounding is done away from 0 (so, for example, ``round(0.5)`` is ``1.0`` and 1248 ``round(-0.5)`` is ``-1.0``). 1249 1250 1251 .. note:: 1252 1253 The behavior of :func:`round` for floats can be surprising: for example, 1254 ``round(2.675, 2)`` gives ``2.67`` instead of the expected ``2.68``. 1255 This is not a bug: it's a result of the fact that most decimal fractions 1256 can't be represented exactly as a float. See :ref:`tut-fp-issues` for 1257 more information. 1258 1259 1260 .. _func-set: 1261 .. class:: set([iterable]) 1262 :noindex: 1263 1264 Return a new :class:`set` object, optionally with elements taken from 1265 *iterable*. ``set`` is a built-in class. See :class:`set` and 1266 :ref:`types-set` for documentation about this class. 1267 1268 For other containers see the built-in :class:`frozenset`, :class:`list`, 1269 :class:`tuple`, and :class:`dict` classes, as well as the :mod:`collections` 1270 module. 1271 1272 .. versionadded:: 2.4 1273 1274 1275 .. function:: setattr(object, name, value) 1276 1277 This is the counterpart of :func:`getattr`. The arguments are an object, a 1278 string and an arbitrary value. The string may name an existing attribute or a 1279 new attribute. The function assigns the value to the attribute, provided the 1280 object allows it. For example, ``setattr(x, 'foobar', 123)`` is equivalent to 1281 ``x.foobar = 123``. 1282 1283 1284 .. class:: slice(stop) 1285 slice(start, stop[, step]) 1286 1287 .. index:: single: Numerical Python 1288 1289 Return a :term:`slice` object representing the set of indices specified by 1290 ``range(start, stop, step)``. The *start* and *step* arguments default to 1291 ``None``. Slice objects have read-only data attributes :attr:`~slice.start`, 1292 :attr:`~slice.stop` and :attr:`~slice.step` which merely return the argument 1293 values (or their default). They have no other explicit functionality; 1294 however they are used by Numerical Python and other third party extensions. 1295 Slice objects are also generated when extended indexing syntax is used. For 1296 example: ``a[start:stop:step]`` or ``a[start:stop, i]``. See 1297 :func:`itertools.islice` for an alternate version that returns an iterator. 1298 1299 1300 .. function:: sorted(iterable[, cmp[, key[, reverse]]]) 1301 1302 Return a new sorted list from the items in *iterable*. 1303 1304 The optional arguments *cmp*, *key*, and *reverse* have the same meaning as 1305 those for the :meth:`list.sort` method (described in section 1306 :ref:`typesseq-mutable`). 1307 1308 *cmp* specifies a custom comparison function of two arguments (iterable 1309 elements) which should return a negative, zero or positive number depending on 1310 whether the first argument is considered smaller than, equal to, or larger than 1311 the second argument: ``cmp=lambda x,y: cmp(x.lower(), y.lower())``. The default 1312 value is ``None``. 1313 1314 *key* specifies a function of one argument that is used to extract a comparison 1315 key from each list element: ``key=str.lower``. The default value is ``None`` 1316 (compare the elements directly). 1317 1318 *reverse* is a boolean value. If set to ``True``, then the list elements are 1319 sorted as if each comparison were reversed. 1320 1321 In general, the *key* and *reverse* conversion processes are much faster 1322 than specifying an equivalent *cmp* function. This is because *cmp* is 1323 called multiple times for each list element while *key* and *reverse* touch 1324 each element only once. Use :func:`functools.cmp_to_key` to convert an 1325 old-style *cmp* function to a *key* function. 1326 1327 The built-in :func:`sorted` function is guaranteed to be stable. A sort is 1328 stable if it guarantees not to change the relative order of elements that 1329 compare equal --- this is helpful for sorting in multiple passes (for 1330 example, sort by department, then by salary grade). 1331 1332 For sorting examples and a brief sorting tutorial, see :ref:`sortinghowto`. 1333 1334 .. versionadded:: 2.4 1335 1336 1337 .. function:: staticmethod(function) 1338 1339 Return a static method for *function*. 1340 1341 A static method does not receive an implicit first argument. To declare a static 1342 method, use this idiom:: 1343 1344 class C(object): 1345 @staticmethod 1346 def f(arg1, arg2, ...): 1347 ... 1348 1349 The ``@staticmethod`` form is a function :term:`decorator` -- see the 1350 description of function definitions in :ref:`function` for details. 1351 1352 It can be called either on the class (such as ``C.f()``) or on an instance (such 1353 as ``C().f()``). The instance is ignored except for its class. 1354 1355 Static methods in Python are similar to those found in Java or C++. Also see 1356 :func:`classmethod` for a variant that is useful for creating alternate 1357 class constructors. 1358 1359 For more information on static methods, consult the documentation on the 1360 standard type hierarchy in :ref:`types`. 1361 1362 .. versionadded:: 2.2 1363 1364 .. versionchanged:: 2.4 1365 Function decorator syntax added. 1366 1367 1368 .. class:: str(object='') 1369 1370 Return a string containing a nicely printable representation of an object. For 1371 strings, this returns the string itself. The difference with ``repr(object)`` 1372 is that ``str(object)`` does not always attempt to return a string that is 1373 acceptable to :func:`eval`; its goal is to return a printable string. If no 1374 argument is given, returns the empty string, ``''``. 1375 1376 For more information on strings see :ref:`typesseq` which describes sequence 1377 functionality (strings are sequences), and also the string-specific methods 1378 described in the :ref:`string-methods` section. To output formatted strings 1379 use template strings or the ``%`` operator described in the 1380 :ref:`string-formatting` section. In addition see the :ref:`stringservices` 1381 section. See also :func:`unicode`. 1382 1383 1384 .. function:: sum(iterable[, start]) 1385 1386 Sums *start* and the items of an *iterable* from left to right and returns the 1387 total. *start* defaults to ``0``. The *iterable*'s items are normally numbers, 1388 and the start value is not allowed to be a string. 1389 1390 For some use cases, there are good alternatives to :func:`sum`. 1391 The preferred, fast way to concatenate a sequence of strings is by calling 1392 ``''.join(sequence)``. To add floating point values with extended precision, 1393 see :func:`math.fsum`\. To concatenate a series of iterables, consider using 1394 :func:`itertools.chain`. 1395 1396 .. versionadded:: 2.3 1397 1398 1399 .. function:: super(type[, object-or-type]) 1400 1401 Return a proxy object that delegates method calls to a parent or sibling 1402 class of *type*. This is useful for accessing inherited methods that have 1403 been overridden in a class. The search order is same as that used by 1404 :func:`getattr` except that the *type* itself is skipped. 1405 1406 The :attr:`~class.__mro__` attribute of the *type* lists the method 1407 resolution search order used by both :func:`getattr` and :func:`super`. The 1408 attribute is dynamic and can change whenever the inheritance hierarchy is 1409 updated. 1410 1411 If the second argument is omitted, the super object returned is unbound. If 1412 the second argument is an object, ``isinstance(obj, type)`` must be true. If 1413 the second argument is a type, ``issubclass(type2, type)`` must be true (this 1414 is useful for classmethods). 1415 1416 .. note:: 1417 :func:`super` only works for :term:`new-style class`\es. 1418 1419 There are two typical use cases for *super*. In a class hierarchy with 1420 single inheritance, *super* can be used to refer to parent classes without 1421 naming them explicitly, thus making the code more maintainable. This use 1422 closely parallels the use of *super* in other programming languages. 1423 1424 The second use case is to support cooperative multiple inheritance in a 1425 dynamic execution environment. This use case is unique to Python and is 1426 not found in statically compiled languages or languages that only support 1427 single inheritance. This makes it possible to implement "diamond diagrams" 1428 where multiple base classes implement the same method. Good design dictates 1429 that this method have the same calling signature in every case (because the 1430 order of calls is determined at runtime, because that order adapts 1431 to changes in the class hierarchy, and because that order can include 1432 sibling classes that are unknown prior to runtime). 1433 1434 For both use cases, a typical superclass call looks like this:: 1435 1436 class C(B): 1437 def method(self, arg): 1438 super(C, self).method(arg) 1439 1440 Note that :func:`super` is implemented as part of the binding process for 1441 explicit dotted attribute lookups such as ``super().__getitem__(name)``. 1442 It does so by implementing its own :meth:`__getattribute__` method for searching 1443 classes in a predictable order that supports cooperative multiple inheritance. 1444 Accordingly, :func:`super` is undefined for implicit lookups using statements or 1445 operators such as ``super()[name]``. 1446 1447 Also note that :func:`super` is not limited to use inside methods. The two 1448 argument form specifies the arguments exactly and makes the appropriate 1449 references. 1450 1451 For practical suggestions on how to design cooperative classes using 1452 :func:`super`, see `guide to using super() 1453 <https://rhettinger.wordpress.com/2011/05/26/super-considered-super/>`_. 1454 1455 .. versionadded:: 2.2 1456 1457 1458 .. function:: tuple([iterable]) 1459 1460 Return a tuple whose items are the same and in the same order as *iterable*'s 1461 items. *iterable* may be a sequence, a container that supports iteration, or an 1462 iterator object. If *iterable* is already a tuple, it is returned unchanged. 1463 For instance, ``tuple('abc')`` returns ``('a', 'b', 'c')`` and ``tuple([1, 2, 1464 3])`` returns ``(1, 2, 3)``. If no argument is given, returns a new empty 1465 tuple, ``()``. 1466 1467 :class:`tuple` is an immutable sequence type, as documented in 1468 :ref:`typesseq`. For other containers see the built in :class:`dict`, 1469 :class:`list`, and :class:`set` classes, and the :mod:`collections` module. 1470 1471 1472 .. class:: type(object) 1473 type(name, bases, dict) 1474 1475 .. index:: object: type 1476 1477 With one argument, return the type of an *object*. The return value is a 1478 type object. The :func:`isinstance` built-in function is recommended for 1479 testing the type of an object. 1480 1481 With three arguments, return a new type object. This is essentially a 1482 dynamic form of the :keyword:`class` statement. The *name* string is the 1483 class name and becomes the :attr:`~definition.__name__` attribute; the *bases* tuple 1484 itemizes the base classes and becomes the :attr:`~class.__bases__` attribute; 1485 and the *dict* dictionary is the namespace containing definitions for class 1486 body and becomes the :attr:`~object.__dict__` attribute. For example, the 1487 following two statements create identical :class:`type` objects: 1488 1489 >>> class X(object): 1490 ... a = 1 1491 ... 1492 >>> X = type('X', (object,), dict(a=1)) 1493 1494 .. versionadded:: 2.2 1495 1496 1497 .. function:: unichr(i) 1498 1499 Return the Unicode string of one character whose Unicode code is the integer 1500 *i*. For example, ``unichr(97)`` returns the string ``u'a'``. This is the 1501 inverse of :func:`ord` for Unicode strings. The valid range for the argument 1502 depends how Python was configured -- it may be either UCS2 [0..0xFFFF] or UCS4 1503 [0..0x10FFFF]. :exc:`ValueError` is raised otherwise. For ASCII and 8-bit 1504 strings see :func:`chr`. 1505 1506 .. versionadded:: 2.0 1507 1508 1509 .. function:: unicode(object='') 1510 unicode(object[, encoding [, errors]]) 1511 1512 Return the Unicode string version of *object* using one of the following modes: 1513 1514 If *encoding* and/or *errors* are given, ``unicode()`` will decode the object 1515 which can either be an 8-bit string or a character buffer using the codec for 1516 *encoding*. The *encoding* parameter is a string giving the name of an encoding; 1517 if the encoding is not known, :exc:`LookupError` is raised. Error handling is 1518 done according to *errors*; this specifies the treatment of characters which are 1519 invalid in the input encoding. If *errors* is ``'strict'`` (the default), a 1520 :exc:`ValueError` is raised on errors, while a value of ``'ignore'`` causes 1521 errors to be silently ignored, and a value of ``'replace'`` causes the official 1522 Unicode replacement character, ``U+FFFD``, to be used to replace input 1523 characters which cannot be decoded. See also the :mod:`codecs` module. 1524 1525 If no optional parameters are given, ``unicode()`` will mimic the behaviour of 1526 ``str()`` except that it returns Unicode strings instead of 8-bit strings. More 1527 precisely, if *object* is a Unicode string or subclass it will return that 1528 Unicode string without any additional decoding applied. 1529 1530 For objects which provide a :meth:`__unicode__` method, it will call this method 1531 without arguments to create a Unicode string. For all other objects, the 8-bit 1532 string version or representation is requested and then converted to a Unicode 1533 string using the codec for the default encoding in ``'strict'`` mode. 1534 1535 For more information on Unicode strings see :ref:`typesseq` which describes 1536 sequence functionality (Unicode strings are sequences), and also the 1537 string-specific methods described in the :ref:`string-methods` section. To 1538 output formatted strings use template strings or the ``%`` operator described 1539 in the :ref:`string-formatting` section. In addition see the 1540 :ref:`stringservices` section. See also :func:`str`. 1541 1542 .. versionadded:: 2.0 1543 1544 .. versionchanged:: 2.2 1545 Support for :meth:`__unicode__` added. 1546 1547 1548 .. function:: vars([object]) 1549 1550 Return the :attr:`~object.__dict__` attribute for a module, class, instance, 1551 or any other object with a :attr:`~object.__dict__` attribute. 1552 1553 Objects such as modules and instances have an updateable :attr:`~object.__dict__` 1554 attribute; however, other objects may have write restrictions on their 1555 :attr:`~object.__dict__` attributes (for example, new-style classes use a 1556 dictproxy to prevent direct dictionary updates). 1557 1558 Without an argument, :func:`vars` acts like :func:`locals`. Note, the 1559 locals dictionary is only useful for reads since updates to the locals 1560 dictionary are ignored. 1561 1562 1563 .. function:: xrange(stop) 1564 xrange(start, stop[, step]) 1565 1566 This function is very similar to :func:`range`, but returns an :ref:`xrange 1567 object <typesseq-xrange>` 1568 instead of a list. This is an opaque sequence type which yields the same values 1569 as the corresponding list, without actually storing them all simultaneously. 1570 The advantage of :func:`xrange` over :func:`range` is minimal (since 1571 :func:`xrange` still has to create the values when asked for them) except when a 1572 very large range is used on a memory-starved machine or when all of the range's 1573 elements are never used (such as when the loop is usually terminated with 1574 :keyword:`break`). For more information on xrange objects, see 1575 :ref:`typesseq-xrange` and :ref:`typesseq`. 1576 1577 .. impl-detail:: 1578 1579 :func:`xrange` is intended to be simple and fast. Implementations may 1580 impose restrictions to achieve this. The C implementation of Python 1581 restricts all arguments to native C longs ("short" Python integers), and 1582 also requires that the number of elements fit in a native C long. If a 1583 larger range is needed, an alternate version can be crafted using the 1584 :mod:`itertools` module: ``islice(count(start, step), 1585 (stop-start+step-1+2*(step<0))//step)``. 1586 1587 1588 .. function:: zip([iterable, ...]) 1589 1590 This function returns a list of tuples, where the *i*-th tuple contains the 1591 *i*-th element from each of the argument sequences or iterables. The returned 1592 list is truncated in length to the length of the shortest argument sequence. 1593 When there are multiple arguments which are all of the same length, :func:`zip` 1594 is similar to :func:`map` with an initial argument of ``None``. With a single 1595 sequence argument, it returns a list of 1-tuples. With no arguments, it returns 1596 an empty list. 1597 1598 The left-to-right evaluation order of the iterables is guaranteed. This 1599 makes possible an idiom for clustering a data series into n-length groups 1600 using ``zip(*[iter(s)]*n)``. 1601 1602 :func:`zip` in conjunction with the ``*`` operator can be used to unzip a 1603 list:: 1604 1605 >>> x = [1, 2, 3] 1606 >>> y = [4, 5, 6] 1607 >>> zipped = zip(x, y) 1608 >>> zipped 1609 [(1, 4), (2, 5), (3, 6)] 1610 >>> x2, y2 = zip(*zipped) 1611 >>> x == list(x2) and y == list(y2) 1612 True 1613 1614 .. versionadded:: 2.0 1615 1616 .. versionchanged:: 2.4 1617 Formerly, :func:`zip` required at least one argument and ``zip()`` raised a 1618 :exc:`TypeError` instead of returning an empty list. 1619 1620 1621 .. function:: __import__(name[, globals[, locals[, fromlist[, level]]]]) 1622 1623 .. index:: 1624 statement: import 1625 module: imp 1626 1627 .. note:: 1628 1629 This is an advanced function that is not needed in everyday Python 1630 programming, unlike :func:`importlib.import_module`. 1631 1632 This function is invoked by the :keyword:`import` statement. It can be 1633 replaced (by importing the :mod:`__builtin__` module and assigning to 1634 ``__builtin__.__import__``) in order to change semantics of the 1635 :keyword:`import` statement, but nowadays it is usually simpler to use import 1636 hooks (see :pep:`302`). Direct use of :func:`__import__` is rare, except in 1637 cases where you want to import a module whose name is only known at runtime. 1638 1639 The function imports the module *name*, potentially using the given *globals* 1640 and *locals* to determine how to interpret the name in a package context. 1641 The *fromlist* gives the names of objects or submodules that should be 1642 imported from the module given by *name*. The standard implementation does 1643 not use its *locals* argument at all, and uses its *globals* only to 1644 determine the package context of the :keyword:`import` statement. 1645 1646 *level* specifies whether to use absolute or relative imports. The default 1647 is ``-1`` which indicates both absolute and relative imports will be 1648 attempted. ``0`` means only perform absolute imports. Positive values for 1649 *level* indicate the number of parent directories to search relative to the 1650 directory of the module calling :func:`__import__`. 1651 1652 When the *name* variable is of the form ``package.module``, normally, the 1653 top-level package (the name up till the first dot) is returned, *not* the 1654 module named by *name*. However, when a non-empty *fromlist* argument is 1655 given, the module named by *name* is returned. 1656 1657 For example, the statement ``import spam`` results in bytecode resembling the 1658 following code:: 1659 1660 spam = __import__('spam', globals(), locals(), [], -1) 1661 1662 The statement ``import spam.ham`` results in this call:: 1663 1664 spam = __import__('spam.ham', globals(), locals(), [], -1) 1665 1666 Note how :func:`__import__` returns the toplevel module here because this is 1667 the object that is bound to a name by the :keyword:`import` statement. 1668 1669 On the other hand, the statement ``from spam.ham import eggs, sausage as 1670 saus`` results in :: 1671 1672 _temp = __import__('spam.ham', globals(), locals(), ['eggs', 'sausage'], -1) 1673 eggs = _temp.eggs 1674 saus = _temp.sausage 1675 1676 Here, the ``spam.ham`` module is returned from :func:`__import__`. From this 1677 object, the names to import are retrieved and assigned to their respective 1678 names. 1679 1680 If you simply want to import a module (potentially within a package) by name, 1681 use :func:`importlib.import_module`. 1682 1683 1684 .. versionchanged:: 2.5 1685 The level parameter was added. 1686 1687 .. versionchanged:: 2.5 1688 Keyword support for parameters was added. 1689 1690 .. --------------------------------------------------------------------------- 1691 1692 1693 .. _non-essential-built-in-funcs: 1694 1695 Non-essential Built-in Functions 1696 ================================ 1697 1698 There are several built-in functions that are no longer essential to learn, know 1699 or use in modern Python programming. They have been kept here to maintain 1700 backwards compatibility with programs written for older versions of Python. 1701 1702 Python programmers, trainers, students and book writers should feel free to 1703 bypass these functions without concerns about missing something important. 1704 1705 1706 .. function:: apply(function, args[, keywords]) 1707 1708 The *function* argument must be a callable object (a user-defined or built-in 1709 function or method, or a class object) and the *args* argument must be a 1710 sequence. The *function* is called with *args* as the argument list; the number 1711 of arguments is the length of the tuple. If the optional *keywords* argument is 1712 present, it must be a dictionary whose keys are strings. It specifies keyword 1713 arguments to be added to the end of the argument list. Calling :func:`apply` is 1714 different from just calling ``function(args)``, since in that case there is 1715 always exactly one argument. The use of :func:`apply` is equivalent to 1716 ``function(*args, **keywords)``. 1717 1718 .. deprecated:: 2.3 1719 Use ``function(*args, **keywords)`` instead of 1720 ``apply(function, args, keywords)`` (see :ref:`tut-unpacking-arguments`). 1721 1722 1723 .. function:: buffer(object[, offset[, size]]) 1724 1725 The *object* argument must be an object that supports the buffer call interface 1726 (such as strings, arrays, and buffers). A new buffer object will be created 1727 which references the *object* argument. The buffer object will be a slice from 1728 the beginning of *object* (or from the specified *offset*). The slice will 1729 extend to the end of *object* (or will have a length given by the *size* 1730 argument). 1731 1732 1733 .. function:: coerce(x, y) 1734 1735 Return a tuple consisting of the two numeric arguments converted to a common 1736 type, using the same rules as used by arithmetic operations. If coercion is not 1737 possible, raise :exc:`TypeError`. 1738 1739 1740 .. function:: intern(string) 1741 1742 Enter *string* in the table of "interned" strings and return the interned string 1743 -- which is *string* itself or a copy. Interning strings is useful to gain a 1744 little performance on dictionary lookup -- if the keys in a dictionary are 1745 interned, and the lookup key is interned, the key comparisons (after hashing) 1746 can be done by a pointer compare instead of a string compare. Normally, the 1747 names used in Python programs are automatically interned, and the dictionaries 1748 used to hold module, class or instance attributes have interned keys. 1749 1750 .. versionchanged:: 2.3 1751 Interned strings are not immortal (like they used to be in Python 2.2 and 1752 before); you must keep a reference to the return value of :func:`intern` around 1753 to benefit from it. 1754 1755 .. rubric:: Footnotes 1756 1757 .. [#] It is used relatively rarely so does not warrant being made into a statement. 1758 1759 .. [#] Specifying a buffer size currently has no effect on systems that don't have 1760 :c:func:`setvbuf`. The interface to specify the buffer size is not done using a 1761 method that calls :c:func:`setvbuf`, because that may dump core when called after 1762 any I/O has been performed, and there's no reliable way to determine whether 1763 this is the case. 1764 1765 .. [#] In the current implementation, local variable bindings cannot normally be 1766 affected this way, but variables retrieved from other scopes (such as modules) 1767 can be. This may change. 1768