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