Gecko [ fernandoquevedodop.com ]

Name	Size	Permission
basic.css	14.32 KB	-rw-r--r--
caret-down.svg	245 B	-rw-r--r--
changelog_search.js	1.85 KB	-rw-r--r--
classic.css	4.3 KB	-rw-r--r--
copybutton.js	2.8 KB	-rw-r--r--
default.css	28 B	-rw-r--r--
doctools.js	9.4 KB	-rw-r--r--
documentation_options.js	357 B	-rw-r--r--
file.png	286 B	-rw-r--r--
glossary.json	139.12 KB	-rw-r--r--
jquery.js	281.79 KB	-rw-r--r--
language_data.js	10.6 KB	-rw-r--r--
menu.js	2.08 KB	-rw-r--r--
minus.png	90 B	-rw-r--r--
opensearch.xml	539 B	-rw-r--r--
plus.png	90 B	-rw-r--r--
py.png	668 B	-rw-r--r--
py.svg	1.99 KB	-rw-r--r--
pydoctheme.css	10.38 KB	-rw-r--r--
pygments.css	4.71 KB	-rw-r--r--
searchtools.js	16.55 KB	-rw-r--r--
sidebar.js	4.25 KB	-rw-r--r--
underscore.js	66.79 KB	-rw-r--r--

Code Editor : glossary.json

{">>>": {"title": ">>>", "body": "<main>\n<dd>The default Python prompt of the interactive shell. Often seen for code\nexamples which can be executed interactively in the interpreter.\n</dd>\n</main>\n"}, "...": {"title": "...", "body": "<main>\n<dd>Can refer to:\n<ul class=\"simple\">\n<li>The default Python prompt of the interactive shell when entering the\ncode for an indented code block, when within a pair of matching left and\nright delimiters (parentheses, square brackets, curly braces or triple\nquotes), or after specifying a decorator.</li>\n<li>The <a class=\"reference internal\" href=\"library/constants.html#Ellipsis\" title=\"Ellipsis\"><code class=\"xref py py-const docutils literal notranslate\">Ellipsis</code></a> built-in constant.</li>\n</ul>\n</dd>\n</main>\n"}, "2to3": {"title": "2to3", "body": "<main>\n<dd>A tool that tries to convert Python 2.x code to Python 3.x code by\nhandling most of the incompatibilities which can be detected by parsing the\nsource and traversing the parse tree.\n2to3 is available in the standard library as <a class=\"reference internal\" href=\"library/2to3.html#module-lib2to3\" title=\"lib2to3: The 2to3 library\"><code class=\"xref py py-mod docutils literal notranslate\">lib2to3</code></a>; a standalone\nentry point is provided as <code class=\"file docutils literal notranslate\">Tools/scripts/2to3</code>. See\n<a class=\"reference internal\" href=\"library/2to3.html#to3-reference\">2to3 \u2014 Automated Python 2 to 3 code translation</a>.\n</dd>\n</main>\n"}, "abstract base class": {"title": "abstract base class", "body": "<main>\n<dd>Abstract base classes complement <a class=\"reference internal\" href=\"#term-duck-typing\">duck-typing</a> by\nproviding a way to define interfaces when other techniques like\n<a class=\"reference internal\" href=\"library/functions.html#hasattr\" title=\"hasattr\"><code class=\"xref py py-func docutils literal notranslate\">hasattr()</code></a> would be clumsy or subtly wrong (for example with\n<a class=\"reference internal\" href=\"reference/datamodel.html#special-lookup\">magic methods</a>). ABCs introduce virtual\nsubclasses, which are classes that don\u2019t inherit from a class but are\nstill recognized by <a class=\"reference internal\" href=\"library/functions.html#isinstance\" title=\"isinstance\"><code class=\"xref py py-func docutils literal notranslate\">isinstance()</code></a> and <a class=\"reference internal\" href=\"library/functions.html#issubclass\" title=\"issubclass\"><code class=\"xref py py-func docutils literal notranslate\">issubclass()</code></a>; see the\n<a class=\"reference internal\" href=\"library/abc.html#module-abc\" title=\"abc: Abstract base classes according to :pep:`3119`.\"><code class=\"xref py py-mod docutils literal notranslate\">abc</code></a> module documentation. Python comes with many built-in ABCs for\ndata structures (in the <a class=\"reference internal\" href=\"library/collections.abc.html#module-collections.abc\" title=\"collections.abc: Abstract base classes for containers\"><code class=\"xref py py-mod docutils literal notranslate\">collections.abc</code></a> module), numbers (in the\n<a class=\"reference internal\" href=\"library/numbers.html#module-numbers\" title=\"numbers: Numeric abstract base classes (Complex, Real, Integral, etc.).\"><code class=\"xref py py-mod docutils literal notranslate\">numbers</code></a> module), streams (in the <a class=\"reference internal\" href=\"library/io.html#module-io\" title=\"io: Core tools for working with streams.\"><code class=\"xref py py-mod docutils literal notranslate\">io</code></a> module), import finders\nand loaders (in the <a class=\"reference internal\" href=\"library/importlib.html#module-importlib.abc\" title=\"importlib.abc: Abstract base classes related to import\"><code class=\"xref py py-mod docutils literal notranslate\">importlib.abc</code></a> module). You can create your own\nABCs with the <a class=\"reference internal\" href=\"library/abc.html#module-abc\" title=\"abc: Abstract base classes according to :pep:`3119`.\"><code class=\"xref py py-mod docutils literal notranslate\">abc</code></a> module.\n</dd>\n</main>\n"}, "annotation": {"title": "annotation", "body": "<main>\n<dd>A label associated with a variable, a class\nattribute or a function parameter or return value,\nused by convention as a <a class=\"reference internal\" href=\"#term-type-hint\">type hint</a>.\nAnnotations of local variables cannot be accessed at runtime, but\nannotations of global variables, class attributes, and functions\nare stored in the <code class=\"xref py py-attr docutils literal notranslate\">__annotations__</code>\nspecial attribute of modules, classes, and functions,\nrespectively.\nSee <a class=\"reference internal\" href=\"#term-variable-annotation\">variable annotation</a>, <a class=\"reference internal\" href=\"#term-function-annotation\">function annotation</a>, <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0484\">PEP 484</a>\nand <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0526\">PEP 526</a>, which describe this functionality.\nAlso see <a class=\"reference internal\" href=\"howto/annotations.html#annotations-howto\">Annotations Best Practices</a>\nfor best practices on working with annotations.\n</dd>\n</main>\n"}, "argument": {"title": "argument", "body": "<main>\n<dd>A value passed to a <a class=\"reference internal\" href=\"#term-function\">function</a> (or <a class=\"reference internal\" href=\"#term-method\">method</a>) when calling the\nfunction. There are two kinds of argument:\n<ul>\n<li>keyword argument: an argument preceded by an identifier (e.g.\n<code class=\"docutils literal notranslate\">name=</code>) in a function call or passed as a value in a dictionary\npreceded by <code class=\"docutils literal notranslate\">**</code>. For example, <code class=\"docutils literal notranslate\">3</code> and <code class=\"docutils literal notranslate\">5</code> are both keyword\narguments in the following calls to <a class=\"reference internal\" href=\"library/functions.html#complex\" title=\"complex\"><code class=\"xref py py-func docutils literal notranslate\">complex()</code></a>:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>complex(real=3, imag=5)\ncomplex(**{&#39;real&#39;: 3, &#39;imag&#39;: 5})\n</pre></div>\n</div>\n</li>\n<li>positional argument: an argument that is not a keyword argument.\nPositional arguments can appear at the beginning of an argument list\nand/or be passed as elements of an <a class=\"reference internal\" href=\"#term-iterable\">iterable</a> preceded by <code class=\"docutils literal notranslate\">*</code>.\nFor example, <code class=\"docutils literal notranslate\">3</code> and <code class=\"docutils literal notranslate\">5</code> are both positional arguments in the\nfollowing calls:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>complex(3, 5)\ncomplex(*(3, 5))\n</pre></div>\n</div>\n</li>\n</ul>\nArguments are assigned to the named local variables in a function body.\nSee the <a class=\"reference internal\" href=\"reference/expressions.html#calls\">Calls</a> section for the rules governing this assignment.\nSyntactically, any expression can be used to represent an argument; the\nevaluated value is assigned to the local variable.\nSee also the <a class=\"reference internal\" href=\"#term-parameter\">parameter</a> glossary entry, the FAQ question on\n<a class=\"reference internal\" href=\"faq/programming.html#faq-argument-vs-parameter\">the difference between arguments and parameters</a>, and <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0362\">PEP 362</a>.\n</dd>\n</main>\n"}, "asynchronous context manager": {"title": "asynchronous context manager", "body": "<main>\n<dd>An object which controls the environment seen in an\n<a class=\"reference internal\" href=\"reference/compound_stmts.html#async-with\"><code class=\"xref std std-keyword docutils literal notranslate\">async with</code></a> statement by defining <code class=\"xref py py-meth docutils literal notranslate\">__aenter__()</code> and\n<code class=\"xref py py-meth docutils literal notranslate\">__aexit__()</code> methods. Introduced by <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0492\">PEP 492</a>.\n</dd>\n</main>\n"}, "asynchronous generator": {"title": "asynchronous generator", "body": "<main>\n<dd>A function which returns an <a class=\"reference internal\" href=\"#term-asynchronous-generator-iterator\">asynchronous generator iterator</a>. It\nlooks like a coroutine function defined with <a class=\"reference internal\" href=\"reference/compound_stmts.html#async-def\"><code class=\"xref std std-keyword docutils literal notranslate\">async def</code></a> except\nthat it contains <a class=\"reference internal\" href=\"reference/simple_stmts.html#yield\"><code class=\"xref std std-keyword docutils literal notranslate\">yield</code></a> expressions for producing a series of\nvalues usable in an <a class=\"reference internal\" href=\"reference/compound_stmts.html#async-for\"><code class=\"xref std std-keyword docutils literal notranslate\">async for</code></a> loop.\nUsually refers to an asynchronous generator function, but may refer to an\nasynchronous generator iterator in some contexts. In cases where the\nintended meaning isn\u2019t clear, using the full terms avoids ambiguity.\nAn asynchronous generator function may contain <a class=\"reference internal\" href=\"reference/expressions.html#await\"><code class=\"xref std std-keyword docutils literal notranslate\">await</code></a>\nexpressions as well as <a class=\"reference internal\" href=\"reference/compound_stmts.html#async-for\"><code class=\"xref std std-keyword docutils literal notranslate\">async for</code></a>, and <a class=\"reference internal\" href=\"reference/compound_stmts.html#async-with\"><code class=\"xref std std-keyword docutils literal notranslate\">async with</code></a>\nstatements.\n</dd>\n</main>\n"}, "asynchronous generator iterator": {"title": "asynchronous generator iterator", "body": "<main>\n<dd>An object created by a <a class=\"reference internal\" href=\"#term-asynchronous-generator\">asynchronous generator</a> function.\nThis is an <a class=\"reference internal\" href=\"#term-asynchronous-iterator\">asynchronous iterator</a> which when called using the\n<code class=\"xref py py-meth docutils literal notranslate\">__anext__()</code> method returns an awaitable object which will execute\nthe body of the asynchronous generator function until the next\n<a class=\"reference internal\" href=\"reference/simple_stmts.html#yield\"><code class=\"xref std std-keyword docutils literal notranslate\">yield</code></a> expression.\nEach <a class=\"reference internal\" href=\"reference/simple_stmts.html#yield\"><code class=\"xref std std-keyword docutils literal notranslate\">yield</code></a> temporarily suspends processing, remembering the\nlocation execution state (including local variables and pending\ntry-statements). When the asynchronous generator iterator effectively\nresumes with another awaitable returned by <code class=\"xref py py-meth docutils literal notranslate\">__anext__()</code>, it\npicks up where it left off. See <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0492\">PEP 492</a> and <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0525\">PEP 525</a>.\n</dd>\n</main>\n"}, "asynchronous iterable": {"title": "asynchronous iterable", "body": "<main>\n<dd>An object, that can be used in an <a class=\"reference internal\" href=\"reference/compound_stmts.html#async-for\"><code class=\"xref std std-keyword docutils literal notranslate\">async for</code></a> statement.\nMust return an <a class=\"reference internal\" href=\"#term-asynchronous-iterator\">asynchronous iterator</a> from its\n<code class=\"xref py py-meth docutils literal notranslate\">__aiter__()</code> method. Introduced by <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0492\">PEP 492</a>.\n</dd>\n</main>\n"}, "asynchronous iterator": {"title": "asynchronous iterator", "body": "<main>\n<dd>An object that implements the <code class=\"xref py py-meth docutils literal notranslate\">__aiter__()</code> and <code class=\"xref py py-meth docutils literal notranslate\">__anext__()</code>\nmethods. <code class=\"docutils literal notranslate\">__anext__</code> must return an <a class=\"reference internal\" href=\"#term-awaitable\">awaitable</a> object.\n<a class=\"reference internal\" href=\"reference/compound_stmts.html#async-for\"><code class=\"xref std std-keyword docutils literal notranslate\">async for</code></a> resolves the awaitables returned by an asynchronous\niterator\u2019s <code class=\"xref py py-meth docutils literal notranslate\">__anext__()</code> method until it raises a\n<a class=\"reference internal\" href=\"library/exceptions.html#StopAsyncIteration\" title=\"StopAsyncIteration\"><code class=\"xref py py-exc docutils literal notranslate\">StopAsyncIteration</code></a> exception. Introduced by <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0492\">PEP 492</a>.\n</dd>\n</main>\n"}, "attribute": {"title": "attribute", "body": "<main>\n<dd>A value associated with an object which is usually referenced by name\nusing dotted expressions.\nFor example, if an object o has an attribute\na it would be referenced as o.a.\nIt is possible to give an object an attribute whose name is not an\nidentifier as defined by <a class=\"reference internal\" href=\"reference/lexical_analysis.html#identifiers\">Identifiers and keywords</a>, for example using\n<a class=\"reference internal\" href=\"library/functions.html#setattr\" title=\"setattr\"><code class=\"xref py py-func docutils literal notranslate\">setattr()</code></a>, if the object allows it.\nSuch an attribute will not be accessible using a dotted expression,\nand would instead need to be retrieved with <a class=\"reference internal\" href=\"library/functions.html#getattr\" title=\"getattr\"><code class=\"xref py py-func docutils literal notranslate\">getattr()</code></a>.\n</dd>\n</main>\n"}, "awaitable": {"title": "awaitable", "body": "<main>\n<dd>An object that can be used in an <a class=\"reference internal\" href=\"reference/expressions.html#await\"><code class=\"xref std std-keyword docutils literal notranslate\">await</code></a> expression. Can be\na <a class=\"reference internal\" href=\"#term-coroutine\">coroutine</a> or an object with an <code class=\"xref py py-meth docutils literal notranslate\">__await__()</code> method.\nSee also <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0492\">PEP 492</a>.\n</dd>\n</main>\n"}, "bdfl": {"title": "BDFL", "body": "<main>\n<dd>Benevolent Dictator For Life, a.k.a. <a class=\"reference external\" href=\"https://gvanrossum.github.io/\">Guido van Rossum</a>, Python\u2019s creator.\n</dd>\n</main>\n"}, "binary file": {"title": "binary file", "body": "<main>\n<dd>A <a class=\"reference internal\" href=\"#term-file-object\">file object</a> able to read and write\n<a class=\"reference internal\" href=\"#term-bytes-like-object\">bytes-like objects</a>.\nExamples of binary files are files opened in binary mode (<code class=\"docutils literal notranslate\">'rb'</code>,\n<code class=\"docutils literal notranslate\">'wb'</code> or <code class=\"docutils literal notranslate\">'rb+'</code>), <code class=\"xref py py-data docutils literal notranslate\">sys.stdin.buffer</code>,\n<code class=\"xref py py-data docutils literal notranslate\">sys.stdout.buffer</code>, and instances of <a class=\"reference internal\" href=\"library/io.html#io.BytesIO\" title=\"io.BytesIO\"><code class=\"xref py py-class docutils literal notranslate\">io.BytesIO</code></a> and\n<a class=\"reference internal\" href=\"library/gzip.html#gzip.GzipFile\" title=\"gzip.GzipFile\"><code class=\"xref py py-class docutils literal notranslate\">gzip.GzipFile</code></a>.\nSee also <a class=\"reference internal\" href=\"#term-text-file\">text file</a> for a file object able to read and write\n<a class=\"reference internal\" href=\"library/stdtypes.html#str\" title=\"str\"><code class=\"xref py py-class docutils literal notranslate\">str</code></a> objects.\n</dd>\n</main>\n"}, "borrowed reference": {"title": "borrowed reference", "body": "<main>\n<dd>In Python\u2019s C API, a borrowed reference is a reference to an object.\nIt does not modify the object reference count. It becomes a dangling\npointer if the object is destroyed. For example, a garbage collection can\nremove the last <a class=\"reference internal\" href=\"#term-strong-reference\">strong reference</a> to the object and so destroy it.\nCalling <a class=\"reference internal\" href=\"c-api/refcounting.html#c.Py_INCREF\" title=\"Py_INCREF\"><code class=\"xref c c-func docutils literal notranslate\">Py_INCREF()</code></a> on the <a class=\"reference internal\" href=\"#term-borrowed-reference\">borrowed reference</a> is\nrecommended to convert it to a <a class=\"reference internal\" href=\"#term-strong-reference\">strong reference</a> in-place, except\nwhen the object cannot be destroyed before the last usage of the borrowed\nreference. The <a class=\"reference internal\" href=\"c-api/refcounting.html#c.Py_NewRef\" title=\"Py_NewRef\"><code class=\"xref c c-func docutils literal notranslate\">Py_NewRef()</code></a> function can be used to create a new\n<a class=\"reference internal\" href=\"#term-strong-reference\">strong reference</a>.\n</dd>\n</main>\n"}, "bytes-like object": {"title": "bytes-like object", "body": "<main>\n<dd>An object that supports the <a class=\"reference internal\" href=\"c-api/buffer.html#bufferobjects\">Buffer Protocol</a> and can\nexport a C-<a class=\"reference internal\" href=\"#term-contiguous\">contiguous</a> buffer. This includes all <a class=\"reference internal\" href=\"library/stdtypes.html#bytes\" title=\"bytes\"><code class=\"xref py py-class docutils literal notranslate\">bytes</code></a>,\n<a class=\"reference internal\" href=\"library/stdtypes.html#bytearray\" title=\"bytearray\"><code class=\"xref py py-class docutils literal notranslate\">bytearray</code></a>, and <a class=\"reference internal\" href=\"library/array.html#array.array\" title=\"array.array\"><code class=\"xref py py-class docutils literal notranslate\">array.array</code></a> objects, as well as many\ncommon <a class=\"reference internal\" href=\"library/stdtypes.html#memoryview\" title=\"memoryview\"><code class=\"xref py py-class docutils literal notranslate\">memoryview</code></a> objects. Bytes-like objects can\nbe used for various operations that work with binary data; these include\ncompression, saving to a binary file, and sending over a socket.\nSome operations need the binary data to be mutable. The documentation\noften refers to these as \u201cread-write bytes-like objects\u201d. Example\nmutable buffer objects include <a class=\"reference internal\" href=\"library/stdtypes.html#bytearray\" title=\"bytearray\"><code class=\"xref py py-class docutils literal notranslate\">bytearray</code></a> and a\n<a class=\"reference internal\" href=\"library/stdtypes.html#memoryview\" title=\"memoryview\"><code class=\"xref py py-class docutils literal notranslate\">memoryview</code></a> of a <a class=\"reference internal\" href=\"library/stdtypes.html#bytearray\" title=\"bytearray\"><code class=\"xref py py-class docutils literal notranslate\">bytearray</code></a>.\nOther operations require the binary data to be stored in\nimmutable objects (\u201cread-only bytes-like objects\u201d); examples\nof these include <a class=\"reference internal\" href=\"library/stdtypes.html#bytes\" title=\"bytes\"><code class=\"xref py py-class docutils literal notranslate\">bytes</code></a> and a <a class=\"reference internal\" href=\"library/stdtypes.html#memoryview\" title=\"memoryview\"><code class=\"xref py py-class docutils literal notranslate\">memoryview</code></a>\nof a <a class=\"reference internal\" href=\"library/stdtypes.html#bytes\" title=\"bytes\"><code class=\"xref py py-class docutils literal notranslate\">bytes</code></a> object.\n</dd>\n</main>\n"}, "bytecode": {"title": "bytecode", "body": "<main>\n<dd>Python source code is compiled into bytecode, the internal representation\nof a Python program in the CPython interpreter. The bytecode is also\ncached in <code class=\"docutils literal notranslate\">.pyc</code> files so that executing the same file is\nfaster the second time (recompilation from source to bytecode can be\navoided). This \u201cintermediate language\u201d is said to run on a\n<a class=\"reference internal\" href=\"#term-virtual-machine\">virtual machine</a> that executes the machine code corresponding to\neach bytecode. Do note that bytecodes are not expected to work between\ndifferent Python virtual machines, nor to be stable between Python\nreleases.\nA list of bytecode instructions can be found in the documentation for\n<a class=\"reference internal\" href=\"library/dis.html#bytecodes\">the dis module</a>.\n</dd>\n</main>\n"}, "callable": {"title": "callable", "body": "<main>\n<dd>A callable is an object that can be called, possibly with a set\nof arguments (see <a class=\"reference internal\" href=\"#term-argument\">argument</a>), with the following syntax:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>callable(argument1, argument2, ...)\n</pre></div>\n</div>\nA <a class=\"reference internal\" href=\"#term-function\">function</a>, and by extension a <a class=\"reference internal\" href=\"#term-method\">method</a>, is a callable.\nAn instance of a class that implements the <a class=\"reference internal\" href=\"reference/datamodel.html#object.__call__\" title=\"object.__call__\"><code class=\"xref py py-meth docutils literal notranslate\">__call__()</code></a>\nmethod is also a callable.\n</dd>\n</main>\n"}, "callback": {"title": "callback", "body": "<main>\n<dd>A subroutine function which is passed as an argument to be executed at\nsome point in the future.\n</dd>\n</main>\n"}, "class": {"title": "class", "body": "<main>\n<dd>A template for creating user-defined objects. Class definitions\nnormally contain method definitions which operate on instances of the\nclass.\n</dd>\n</main>\n"}, "class variable": {"title": "class variable", "body": "<main>\n<dd>A variable defined in a class and intended to be modified only at\nclass level (i.e., not in an instance of the class).\n</dd>\n</main>\n"}, "coercion": {"title": "coercion", "body": "<main>\n<dd>The implicit conversion of an instance of one type to another during an\noperation which involves two arguments of the same type. For example,\n<code class=\"docutils literal notranslate\">int(3.15)</code> converts the floating point number to the integer <code class=\"docutils literal notranslate\">3</code>, but\nin <code class=\"docutils literal notranslate\">3+4.5</code>, each argument is of a different type (one int, one float),\nand both must be converted to the same type before they can be added or it\nwill raise a <a class=\"reference internal\" href=\"library/exceptions.html#TypeError\" title=\"TypeError\"><code class=\"xref py py-exc docutils literal notranslate\">TypeError</code></a>. Without coercion, all arguments of even\ncompatible types would have to be normalized to the same value by the\nprogrammer, e.g., <code class=\"docutils literal notranslate\">float(3)+4.5</code> rather than just <code class=\"docutils literal notranslate\">3+4.5</code>.\n</dd>\n</main>\n"}, "complex number": {"title": "complex number", "body": "<main>\n<dd>An extension of the familiar real number system in which all numbers are\nexpressed as a sum of a real part and an imaginary part. Imaginary\nnumbers are real multiples of the imaginary unit (the square root of\n<code class=\"docutils literal notranslate\">-1</code>), often written <code class=\"docutils literal notranslate\">i</code> in mathematics or <code class=\"docutils literal notranslate\">j</code> in\nengineering. Python has built-in support for complex numbers, which are\nwritten with this latter notation; the imaginary part is written with a\n<code class=\"docutils literal notranslate\">j</code> suffix, e.g., <code class=\"docutils literal notranslate\">3+1j</code>. To get access to complex equivalents of the\n<a class=\"reference internal\" href=\"library/math.html#module-math\" title=\"math: Mathematical functions (sin() etc.).\"><code class=\"xref py py-mod docutils literal notranslate\">math</code></a> module, use <a class=\"reference internal\" href=\"library/cmath.html#module-cmath\" title=\"cmath: Mathematical functions for complex numbers.\"><code class=\"xref py py-mod docutils literal notranslate\">cmath</code></a>. Use of complex numbers is a fairly\nadvanced mathematical feature. If you\u2019re not aware of a need for them,\nit\u2019s almost certain you can safely ignore them.\n</dd>\n</main>\n"}, "context manager": {"title": "context manager", "body": "<main>\n<dd>An object which controls the environment seen in a <a class=\"reference internal\" href=\"reference/compound_stmts.html#with\"><code class=\"xref std std-keyword docutils literal notranslate\">with</code></a>\nstatement by defining <code class=\"xref py py-meth docutils literal notranslate\">__enter__()</code> and <code class=\"xref py py-meth docutils literal notranslate\">__exit__()</code> methods.\nSee <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0343\">PEP 343</a>.\n</dd>\n</main>\n"}, "context variable": {"title": "context variable", "body": "<main>\n<dd>A variable which can have different values depending on its context.\nThis is similar to Thread-Local Storage in which each execution\nthread may have a different value for a variable. However, with context\nvariables, there may be several contexts in one execution thread and the\nmain usage for context variables is to keep track of variables in\nconcurrent asynchronous tasks.\nSee <a class=\"reference internal\" href=\"library/contextvars.html#module-contextvars\" title=\"contextvars: Context Variables\"><code class=\"xref py py-mod docutils literal notranslate\">contextvars</code></a>.\n</dd>\n</main>\n"}, "contiguous": {"title": "contiguous", "body": "<main>\n<dd>A buffer is considered contiguous exactly if it is either\nC-contiguous or Fortran contiguous. Zero-dimensional buffers are\nC and Fortran contiguous. In one-dimensional arrays, the items\nmust be laid out in memory next to each other, in order of\nincreasing indexes starting from zero. In multidimensional\nC-contiguous arrays, the last index varies the fastest when\nvisiting items in order of memory address. However, in\nFortran contiguous arrays, the first index varies the fastest.\n</dd>\n</main>\n"}, "coroutine": {"title": "coroutine", "body": "<main>\n<dd>Coroutines are a more generalized form of subroutines. Subroutines are\nentered at one point and exited at another point. Coroutines can be\nentered, exited, and resumed at many different points. They can be\nimplemented with the <a class=\"reference internal\" href=\"reference/compound_stmts.html#async-def\"><code class=\"xref std std-keyword docutils literal notranslate\">async def</code></a> statement. See also\n<a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0492\">PEP 492</a>.\n</dd>\n</main>\n"}, "coroutine function": {"title": "coroutine function", "body": "<main>\n<dd>A function which returns a <a class=\"reference internal\" href=\"#term-coroutine\">coroutine</a> object. A coroutine\nfunction may be defined with the <a class=\"reference internal\" href=\"reference/compound_stmts.html#async-def\"><code class=\"xref std std-keyword docutils literal notranslate\">async def</code></a> statement,\nand may contain <a class=\"reference internal\" href=\"reference/expressions.html#await\"><code class=\"xref std std-keyword docutils literal notranslate\">await</code></a>, <a class=\"reference internal\" href=\"reference/compound_stmts.html#async-for\"><code class=\"xref std std-keyword docutils literal notranslate\">async for</code></a>, and\n<a class=\"reference internal\" href=\"reference/compound_stmts.html#async-with\"><code class=\"xref std std-keyword docutils literal notranslate\">async with</code></a> keywords. These were introduced\nby <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0492\">PEP 492</a>.\n</dd>\n</main>\n"}, "cpython": {"title": "CPython", "body": "<main>\n<dd>The canonical implementation of the Python programming language, as\ndistributed on <a class=\"reference external\" href=\"https://www.python.org\">python.org</a>. The term \u201cCPython\u201d\nis used when necessary to distinguish this implementation from others\nsuch as Jython or IronPython.\n</dd>\n</main>\n"}, "decorator": {"title": "decorator", "body": "<main>\n<dd>A function returning another function, usually applied as a function\ntransformation using the <code class=\"docutils literal notranslate\">&#64;wrapper</code> syntax. Common examples for\ndecorators are <a class=\"reference internal\" href=\"library/functions.html#classmethod\" title=\"classmethod\"><code class=\"xref py py-func docutils literal notranslate\">classmethod()</code></a> and <a class=\"reference internal\" href=\"library/functions.html#staticmethod\" title=\"staticmethod\"><code class=\"xref py py-func docutils literal notranslate\">staticmethod()</code></a>.\nThe decorator syntax is merely syntactic sugar, the following two\nfunction definitions are semantically equivalent:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>def f(arg):\n ...\nf = staticmethod(f)\n\n@staticmethod\ndef f(arg):\n ...\n</pre></div>\n</div>\nThe same concept exists for classes, but is less commonly used there. See\nthe documentation for <a class=\"reference internal\" href=\"reference/compound_stmts.html#function\">function definitions</a> and\n<a class=\"reference internal\" href=\"reference/compound_stmts.html#class\">class definitions</a> for more about decorators.\n</dd>\n</main>\n"}, "descriptor": {"title": "descriptor", "body": "<main>\n<dd>Any object which defines the methods <code class=\"xref py py-meth docutils literal notranslate\">__get__()</code>, <code class=\"xref py py-meth docutils literal notranslate\">__set__()</code>, or\n<code class=\"xref py py-meth docutils literal notranslate\">__delete__()</code>. When a class attribute is a descriptor, its special\nbinding behavior is triggered upon attribute lookup. Normally, using\na.b to get, set or delete an attribute looks up the object named b in\nthe class dictionary for a, but if b is a descriptor, the respective\ndescriptor method gets called. Understanding descriptors is a key to a\ndeep understanding of Python because they are the basis for many features\nincluding functions, methods, properties, class methods, static methods,\nand reference to super classes.\nFor more information about descriptors\u2019 methods, see <a class=\"reference internal\" href=\"reference/datamodel.html#descriptors\">Implementing Descriptors</a>\nor the <a class=\"reference internal\" href=\"howto/descriptor.html#descriptorhowto\">Descriptor How To Guide</a>.\n</dd>\n</main>\n"}, "dictionary": {"title": "dictionary", "body": "<main>\n<dd>An associative array, where arbitrary keys are mapped to values. The\nkeys can be any object with <code class=\"xref py py-meth docutils literal notranslate\">__hash__()</code> and <code class=\"xref py py-meth docutils literal notranslate\">__eq__()</code> methods.\nCalled a hash in Perl.\n</dd>\n</main>\n"}, "dictionary comprehension": {"title": "dictionary comprehension", "body": "<main>\n<dd>A compact way to process all or part of the elements in an iterable and\nreturn a dictionary with the results. <code class=\"docutils literal notranslate\">results = {n: n ** 2 for n in\nrange(10)}</code> generates a dictionary containing key <code class=\"docutils literal notranslate\">n</code> mapped to\nvalue <code class=\"docutils literal notranslate\">n ** 2</code>. See <a class=\"reference internal\" href=\"reference/expressions.html#comprehensions\">Displays for lists, sets and dictionaries</a>.\n</dd>\n</main>\n"}, "dictionary view": {"title": "dictionary view", "body": "<main>\n<dd>The objects returned from <a class=\"reference internal\" href=\"library/stdtypes.html#dict.keys\" title=\"dict.keys\"><code class=\"xref py py-meth docutils literal notranslate\">dict.keys()</code></a>, <a class=\"reference internal\" href=\"library/stdtypes.html#dict.values\" title=\"dict.values\"><code class=\"xref py py-meth docutils literal notranslate\">dict.values()</code></a>, and\n<a class=\"reference internal\" href=\"library/stdtypes.html#dict.items\" title=\"dict.items\"><code class=\"xref py py-meth docutils literal notranslate\">dict.items()</code></a> are called dictionary views. They provide a dynamic\nview on the dictionary\u2019s entries, which means that when the dictionary\nchanges, the view reflects these changes. To force the\ndictionary view to become a full list use <code class=\"docutils literal notranslate\">list(dictview)</code>. See\n<a class=\"reference internal\" href=\"library/stdtypes.html#dict-views\">Dictionary view objects</a>.\n</dd>\n</main>\n"}, "docstring": {"title": "docstring", "body": "<main>\n<dd>A string literal which appears as the first expression in a class,\nfunction or module. While ignored when the suite is executed, it is\nrecognized by the compiler and put into the <code class=\"xref py py-attr docutils literal notranslate\">__doc__</code> attribute\nof the enclosing class, function or module. Since it is available via\nintrospection, it is the canonical place for documentation of the\nobject.\n</dd>\n</main>\n"}, "duck-typing": {"title": "duck-typing", "body": "<main>\n<dd>A programming style which does not look at an object\u2019s type to determine\nif it has the right interface; instead, the method or attribute is simply\ncalled or used (\u201cIf it looks like a duck and quacks like a duck, it\nmust be a duck.\u201d) By emphasizing interfaces rather than specific types,\nwell-designed code improves its flexibility by allowing polymorphic\nsubstitution. Duck-typing avoids tests using <a class=\"reference internal\" href=\"library/functions.html#type\" title=\"type\"><code class=\"xref py py-func docutils literal notranslate\">type()</code></a> or\n<a class=\"reference internal\" href=\"library/functions.html#isinstance\" title=\"isinstance\"><code class=\"xref py py-func docutils literal notranslate\">isinstance()</code></a>. (Note, however, that duck-typing can be complemented\nwith <a class=\"reference internal\" href=\"#term-abstract-base-class\">abstract base classes</a>.) Instead, it\ntypically employs <a class=\"reference internal\" href=\"library/functions.html#hasattr\" title=\"hasattr\"><code class=\"xref py py-func docutils literal notranslate\">hasattr()</code></a> tests or <a class=\"reference internal\" href=\"#term-EAFP\">EAFP</a> programming.\n</dd>\n</main>\n"}, "eafp": {"title": "EAFP", "body": "<main>\n<dd>Easier to ask for forgiveness than permission. This common Python coding\nstyle assumes the existence of valid keys or attributes and catches\nexceptions if the assumption proves false. This clean and fast style is\ncharacterized by the presence of many <a class=\"reference internal\" href=\"reference/compound_stmts.html#try\"><code class=\"xref std std-keyword docutils literal notranslate\">try</code></a> and <a class=\"reference internal\" href=\"reference/compound_stmts.html#except\"><code class=\"xref std std-keyword docutils literal notranslate\">except</code></a>\nstatements. The technique contrasts with the <a class=\"reference internal\" href=\"#term-LBYL\">LBYL</a> style\ncommon to many other languages such as C.\n</dd>\n</main>\n"}, "expression": {"title": "expression", "body": "<main>\n<dd>A piece of syntax which can be evaluated to some value. In other words,\nan expression is an accumulation of expression elements like literals,\nnames, attribute access, operators or function calls which all return a\nvalue. In contrast to many other languages, not all language constructs\nare expressions. There are also <a class=\"reference internal\" href=\"#term-statement\">statement</a>s which cannot be used\nas expressions, such as <a class=\"reference internal\" href=\"reference/compound_stmts.html#while\"><code class=\"xref std std-keyword docutils literal notranslate\">while</code></a>. Assignments are also statements,\nnot expressions.\n</dd>\n</main>\n"}, "extension module": {"title": "extension module", "body": "<main>\n<dd>A module written in C or C++, using Python\u2019s C API to interact with the\ncore and with user code.\n</dd>\n</main>\n"}, "f-string": {"title": "f-string", "body": "<main>\n<dd>String literals prefixed with <code class=\"docutils literal notranslate\">'f'</code> or <code class=\"docutils literal notranslate\">'F'</code> are commonly called\n\u201cf-strings\u201d which is short for\n<a class=\"reference internal\" href=\"reference/lexical_analysis.html#f-strings\">formatted string literals</a>. See also <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0498\">PEP 498</a>.\n</dd>\n</main>\n"}, "file object": {"title": "file object", "body": "<main>\n<dd>An object exposing a file-oriented API (with methods such as\n<code class=\"xref py py-meth docutils literal notranslate\">read()</code> or <code class=\"xref py py-meth docutils literal notranslate\">write()</code>) to an underlying resource. Depending\non the way it was created, a file object can mediate access to a real\non-disk file or to another type of storage or communication device\n(for example standard input/output, in-memory buffers, sockets, pipes,\netc.). File objects are also called file-like objects or\nstreams.\nThere are actually three categories of file objects: raw\n<a class=\"reference internal\" href=\"#term-binary-file\">binary files</a>, buffered\n<a class=\"reference internal\" href=\"#term-binary-file\">binary files</a> and <a class=\"reference internal\" href=\"#term-text-file\">text files</a>.\nTheir interfaces are defined in the <a class=\"reference internal\" href=\"library/io.html#module-io\" title=\"io: Core tools for working with streams.\"><code class=\"xref py py-mod docutils literal notranslate\">io</code></a> module. The canonical\nway to create a file object is by using the <a class=\"reference internal\" href=\"library/functions.html#open\" title=\"open\"><code class=\"xref py py-func docutils literal notranslate\">open()</code></a> function.\n</dd>\n</main>\n"}, "file-like object": {"title": "file-like object", "body": "<main>\n<dd>A synonym for <a class=\"reference internal\" href=\"#term-file-object\">file object</a>.\n</dd>\n</main>\n"}, "filesystem encoding and error handler": {"title": "filesystem encoding and error handler", "body": "<main>\n<dd>Encoding and error handler used by Python to decode bytes from the\noperating system and encode Unicode to the operating system.\nThe filesystem encoding must guarantee to successfully decode all bytes\nbelow 128. If the file system encoding fails to provide this guarantee,\nAPI functions can raise <a class=\"reference internal\" href=\"library/exceptions.html#UnicodeError\" title=\"UnicodeError\"><code class=\"xref py py-exc docutils literal notranslate\">UnicodeError</code></a>.\nThe <a class=\"reference internal\" href=\"library/sys.html#sys.getfilesystemencoding\" title=\"sys.getfilesystemencoding\"><code class=\"xref py py-func docutils literal notranslate\">sys.getfilesystemencoding()</code></a> and\n<a class=\"reference internal\" href=\"library/sys.html#sys.getfilesystemencodeerrors\" title=\"sys.getfilesystemencodeerrors\"><code class=\"xref py py-func docutils literal notranslate\">sys.getfilesystemencodeerrors()</code></a> functions can be used to get the\nfilesystem encoding and error handler.\nThe <a class=\"reference internal\" href=\"#term-filesystem-encoding-and-error-handler\">filesystem encoding and error handler</a> are configured at\nPython startup by the <code class=\"xref c c-func docutils literal notranslate\">PyConfig_Read()</code> function: see\n<a class=\"reference internal\" href=\"c-api/init_config.html#c.PyConfig.filesystem_encoding\" title=\"PyConfig.filesystem_encoding\"><code class=\"xref c c-member docutils literal notranslate\">filesystem_encoding</code></a> and\n<a class=\"reference internal\" href=\"c-api/init_config.html#c.PyConfig.filesystem_errors\" title=\"PyConfig.filesystem_errors\"><code class=\"xref c c-member docutils literal notranslate\">filesystem_errors</code></a> members of <a class=\"reference internal\" href=\"c-api/init_config.html#c.PyConfig\" title=\"PyConfig\"><code class=\"xref c c-type docutils literal notranslate\">PyConfig</code></a>.\nSee also the <a class=\"reference internal\" href=\"#term-locale-encoding\">locale encoding</a>.\n</dd>\n</main>\n"}, "finder": {"title": "finder", "body": "<main>\n<dd>An object that tries to find the <a class=\"reference internal\" href=\"#term-loader\">loader</a> for a module that is\nbeing imported.\nSince Python 3.3, there are two types of finder: <a class=\"reference internal\" href=\"#term-meta-path-finder\">meta path finders</a> for use with <a class=\"reference internal\" href=\"library/sys.html#sys.meta_path\" title=\"sys.meta_path\"><code class=\"xref py py-data docutils literal notranslate\">sys.meta_path</code></a>, and <a class=\"reference internal\" href=\"#term-path-entry-finder\">path\nentry finders</a> for use with <a class=\"reference internal\" href=\"library/sys.html#sys.path_hooks\" title=\"sys.path_hooks\"><code class=\"xref py py-data docutils literal notranslate\">sys.path_hooks</code></a>.\nSee <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0302\">PEP 302</a>, <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0420\">PEP 420</a> and <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0451\">PEP 451</a> for much more detail.\n</dd>\n</main>\n"}, "floor division": {"title": "floor division", "body": "<main>\n<dd>Mathematical division that rounds down to nearest integer. The floor\ndivision operator is <code class=\"docutils literal notranslate\">//</code>. For example, the expression <code class=\"docutils literal notranslate\">11 // 4</code>\nevaluates to <code class=\"docutils literal notranslate\">2</code> in contrast to the <code class=\"docutils literal notranslate\">2.75</code> returned by float true\ndivision. Note that <code class=\"docutils literal notranslate\">(-11) // 4</code> is <code class=\"docutils literal notranslate\">-3</code> because that is <code class=\"docutils literal notranslate\">-2.75</code>\nrounded downward. See <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0238\">PEP 238</a>.\n</dd>\n</main>\n"}, "function": {"title": "function", "body": "<main>\n<dd>A series of statements which returns some value to a caller. It can also\nbe passed zero or more <a class=\"reference internal\" href=\"#term-argument\">arguments</a> which may be used in\nthe execution of the body. See also <a class=\"reference internal\" href=\"#term-parameter\">parameter</a>, <a class=\"reference internal\" href=\"#term-method\">method</a>,\nand the <a class=\"reference internal\" href=\"reference/compound_stmts.html#function\">Function definitions</a> section.\n</dd>\n</main>\n"}, "function annotation": {"title": "function annotation", "body": "<main>\n<dd>An <a class=\"reference internal\" href=\"#term-annotation\">annotation</a> of a function parameter or return value.\nFunction annotations are usually used for\n<a class=\"reference internal\" href=\"#term-type-hint\">type hints</a>: for example, this function is expected to take two\n<a class=\"reference internal\" href=\"library/functions.html#int\" title=\"int\"><code class=\"xref py py-class docutils literal notranslate\">int</code></a> arguments and is also expected to have an <a class=\"reference internal\" href=\"library/functions.html#int\" title=\"int\"><code class=\"xref py py-class docutils literal notranslate\">int</code></a>\nreturn value:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>def sum_two_numbers(a: int, b: int) -&gt; int:\n return a + b\n</pre></div>\n</div>\nFunction annotation syntax is explained in section <a class=\"reference internal\" href=\"reference/compound_stmts.html#function\">Function definitions</a>.\nSee <a class=\"reference internal\" href=\"#term-variable-annotation\">variable annotation</a> and <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0484\">PEP 484</a>,\nwhich describe this functionality.\nAlso see <a class=\"reference internal\" href=\"howto/annotations.html#annotations-howto\">Annotations Best Practices</a>\nfor best practices on working with annotations.\n</dd>\n</main>\n"}, "__future__": {"title": "__future__", "body": "<main>\n<dd>A <a class=\"reference internal\" href=\"reference/simple_stmts.html#future\">future statement</a>, <code class=\"docutils literal notranslate\">from __future__ import &lt;feature&gt;</code>,\ndirects the compiler to compile the current module using syntax or\nsemantics that will become standard in a future release of Python.\nThe <a class=\"reference internal\" href=\"library/__future__.html#module-__future__\" title=\"__future__: Future statement definitions\"><code class=\"xref py py-mod docutils literal notranslate\">__future__</code></a> module documents the possible values of\nfeature. By importing this module and evaluating its variables,\nyou can see when a new feature was first added to the language and\nwhen it will (or did) become the default:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>&gt;&gt;&gt; import __future__\n&gt;&gt;&gt; __future__.division\n_Feature((2, 2, 0, &#39;alpha&#39;, 2), (3, 0, 0, &#39;alpha&#39;, 0), 8192)\n</pre></div>\n</div>\n</dd>\n</main>\n"}, "garbage collection": {"title": "garbage collection", "body": "<main>\n<dd>The process of freeing memory when it is not used anymore. Python\nperforms garbage collection via reference counting and a cyclic garbage\ncollector that is able to detect and break reference cycles. The\ngarbage collector can be controlled using the <a class=\"reference internal\" href=\"library/gc.html#module-gc\" title=\"gc: Interface to the cycle-detecting garbage collector.\"><code class=\"xref py py-mod docutils literal notranslate\">gc</code></a> module.\n</dd>\n</main>\n"}, "generator": {"title": "generator", "body": "<main>\n<dd>A function which returns a <a class=\"reference internal\" href=\"#term-generator-iterator\">generator iterator</a>. It looks like a\nnormal function except that it contains <a class=\"reference internal\" href=\"reference/simple_stmts.html#yield\"><code class=\"xref std std-keyword docutils literal notranslate\">yield</code></a> expressions\nfor producing a series of values usable in a for-loop or that can be\nretrieved one at a time with the <a class=\"reference internal\" href=\"library/functions.html#next\" title=\"next\"><code class=\"xref py py-func docutils literal notranslate\">next()</code></a> function.\nUsually refers to a generator function, but may refer to a\ngenerator iterator in some contexts. In cases where the intended\nmeaning isn\u2019t clear, using the full terms avoids ambiguity.\n</dd>\n</main>\n"}, "generator iterator": {"title": "generator iterator", "body": "<main>\n<dd>An object created by a <a class=\"reference internal\" href=\"#term-generator\">generator</a> function.\nEach <a class=\"reference internal\" href=\"reference/simple_stmts.html#yield\"><code class=\"xref std std-keyword docutils literal notranslate\">yield</code></a> temporarily suspends processing, remembering the\nlocation execution state (including local variables and pending\ntry-statements). When the generator iterator resumes, it picks up where\nit left off (in contrast to functions which start fresh on every\ninvocation).\n</dd>\n</main>\n"}, "generator expression": {"title": "generator expression", "body": "<main>\n<dd>An expression that returns an iterator. It looks like a normal expression\nfollowed by a <code class=\"xref std std-keyword docutils literal notranslate\">for</code> clause defining a loop variable, range,\nand an optional <code class=\"xref std std-keyword docutils literal notranslate\">if</code> clause. The combined expression\ngenerates values for an enclosing function:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>&gt;&gt;&gt; sum(i*i for i in range(10)) # sum of squares 0, 1, 4, ... 81\n285\n</pre></div>\n</div>\n</dd>\n</main>\n"}, "generic function": {"title": "generic function", "body": "<main>\n<dd>A function composed of multiple functions implementing the same operation\nfor different types. Which implementation should be used during a call is\ndetermined by the dispatch algorithm.\nSee also the <a class=\"reference internal\" href=\"#term-single-dispatch\">single dispatch</a> glossary entry, the\n<a class=\"reference internal\" href=\"library/functools.html#functools.singledispatch\" title=\"functools.singledispatch\"><code class=\"xref py py-func docutils literal notranslate\">functools.singledispatch()</code></a> decorator, and <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0443\">PEP 443</a>.\n</dd>\n</main>\n"}, "generic type": {"title": "generic type", "body": "<main>\n<dd>A <a class=\"reference internal\" href=\"#term-type\">type</a> that can be parameterized; typically a\n<a class=\"reference internal\" href=\"reference/datamodel.html#sequence-types\">container class</a> such as <a class=\"reference internal\" href=\"library/stdtypes.html#list\" title=\"list\"><code class=\"xref py py-class docutils literal notranslate\">list</code></a> or\n<a class=\"reference internal\" href=\"library/stdtypes.html#dict\" title=\"dict\"><code class=\"xref py py-class docutils literal notranslate\">dict</code></a>. Used for <a class=\"reference internal\" href=\"#term-type-hint\">type hints</a> and\n<a class=\"reference internal\" href=\"#term-annotation\">annotations</a>.\nFor more details, see <a class=\"reference internal\" href=\"library/stdtypes.html#types-genericalias\">generic alias types</a>,\n<a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0483\">PEP 483</a>, <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0484\">PEP 484</a>, <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0585\">PEP 585</a>, and the <a class=\"reference internal\" href=\"library/typing.html#module-typing\" title=\"typing: Support for type hints (see :pep:`484`).\"><code class=\"xref py py-mod docutils literal notranslate\">typing</code></a> module.\n</dd>\n</main>\n"}, "gil": {"title": "GIL", "body": "<main>\n<dd>See <a class=\"reference internal\" href=\"#term-global-interpreter-lock\">global interpreter lock</a>.\n</dd>\n</main>\n"}, "global interpreter lock": {"title": "global interpreter lock", "body": "<main>\n<dd>The mechanism used by the <a class=\"reference internal\" href=\"#term-CPython\">CPython</a> interpreter to assure that\nonly one thread executes Python <a class=\"reference internal\" href=\"#term-bytecode\">bytecode</a> at a time.\nThis simplifies the CPython implementation by making the object model\n(including critical built-in types such as <a class=\"reference internal\" href=\"library/stdtypes.html#dict\" title=\"dict\"><code class=\"xref py py-class docutils literal notranslate\">dict</code></a>) implicitly\nsafe against concurrent access. Locking the entire interpreter\nmakes it easier for the interpreter to be multi-threaded, at the\nexpense of much of the parallelism afforded by multi-processor\nmachines.\nHowever, some extension modules, either standard or third-party,\nare designed so as to release the GIL when doing computationally intensive\ntasks such as compression or hashing. Also, the GIL is always released\nwhen doing I/O.\nPast efforts to create a \u201cfree-threaded\u201d interpreter (one which locks\nshared data at a much finer granularity) have not been successful\nbecause performance suffered in the common single-processor case. It\nis believed that overcoming this performance issue would make the\nimplementation much more complicated and therefore costlier to maintain.\n</dd>\n</main>\n"}, "hash-based pyc": {"title": "hash-based pyc", "body": "<main>\n<dd>A bytecode cache file that uses the hash rather than the last-modified\ntime of the corresponding source file to determine its validity. See\n<a class=\"reference internal\" href=\"reference/import.html#pyc-invalidation\">Cached bytecode invalidation</a>.\n</dd>\n</main>\n"}, "hashable": {"title": "hashable", "body": "<main>\n<dd>An object is hashable if it has a hash value which never changes during\nits lifetime (it needs a <code class=\"xref py py-meth docutils literal notranslate\">__hash__()</code> method), and can be compared to\nother objects (it needs an <code class=\"xref py py-meth docutils literal notranslate\">__eq__()</code> method). Hashable objects which\ncompare equal must have the same hash value.\nHashability makes an object usable as a dictionary key and a set member,\nbecause these data structures use the hash value internally.\nMost of Python\u2019s immutable built-in objects are hashable; mutable\ncontainers (such as lists or dictionaries) are not; immutable\ncontainers (such as tuples and frozensets) are only hashable if\ntheir elements are hashable. Objects which are\ninstances of user-defined classes are hashable by default. They all\ncompare unequal (except with themselves), and their hash value is derived\nfrom their <a class=\"reference internal\" href=\"library/functions.html#id\" title=\"id\"><code class=\"xref py py-func docutils literal notranslate\">id()</code></a>.\n</dd>\n</main>\n"}, "idle": {"title": "IDLE", "body": "<main>\n<dd>An Integrated Development and Learning Environment for Python.\n<a class=\"reference internal\" href=\"library/idle.html#idle\">IDLE</a> is a basic editor and interpreter environment\nwhich ships with the standard distribution of Python.\n</dd>\n</main>\n"}, "immutable": {"title": "immutable", "body": "<main>\n<dd>An object with a fixed value. Immutable objects include numbers, strings and\ntuples. Such an object cannot be altered. A new object has to\nbe created if a different value has to be stored. They play an important\nrole in places where a constant hash value is needed, for example as a key\nin a dictionary.\n</dd>\n</main>\n"}, "import path": {"title": "import path", "body": "<main>\n<dd>A list of locations (or <a class=\"reference internal\" href=\"#term-path-entry\">path entries</a>) that are\nsearched by the <a class=\"reference internal\" href=\"#term-path-based-finder\">path based finder</a> for modules to import. During\nimport, this list of locations usually comes from <a class=\"reference internal\" href=\"library/sys.html#sys.path\" title=\"sys.path\"><code class=\"xref py py-data docutils literal notranslate\">sys.path</code></a>, but\nfor subpackages it may also come from the parent package\u2019s <code class=\"docutils literal notranslate\">__path__</code>\nattribute.\n</dd>\n</main>\n"}, "importing": {"title": "importing", "body": "<main>\n<dd>The process by which Python code in one module is made available to\nPython code in another module.\n</dd>\n</main>\n"}, "importer": {"title": "importer", "body": "<main>\n<dd>An object that both finds and loads a module; both a\n<a class=\"reference internal\" href=\"#term-finder\">finder</a> and <a class=\"reference internal\" href=\"#term-loader\">loader</a> object.\n</dd>\n</main>\n"}, "interactive": {"title": "interactive", "body": "<main>\n<dd>Python has an interactive interpreter which means you can enter\nstatements and expressions at the interpreter prompt, immediately\nexecute them and see their results. Just launch <code class=\"docutils literal notranslate\">python</code> with no\narguments (possibly by selecting it from your computer\u2019s main\nmenu). It is a very powerful way to test out new ideas or inspect\nmodules and packages (remember <code class=\"docutils literal notranslate\">help(x)</code>).\n</dd>\n</main>\n"}, "interpreted": {"title": "interpreted", "body": "<main>\n<dd>Python is an interpreted language, as opposed to a compiled one,\nthough the distinction can be blurry because of the presence of the\nbytecode compiler. This means that source files can be run directly\nwithout explicitly creating an executable which is then run.\nInterpreted languages typically have a shorter development/debug cycle\nthan compiled ones, though their programs generally also run more\nslowly. See also <a class=\"reference internal\" href=\"#term-interactive\">interactive</a>.\n</dd>\n</main>\n"}, "interpreter shutdown": {"title": "interpreter shutdown", "body": "<main>\n<dd>When asked to shut down, the Python interpreter enters a special phase\nwhere it gradually releases all allocated resources, such as modules\nand various critical internal structures. It also makes several calls\nto the <a class=\"reference internal\" href=\"#term-garbage-collection\">garbage collector</a>. This can trigger\nthe execution of code in user-defined destructors or weakref callbacks.\nCode executed during the shutdown phase can encounter various\nexceptions as the resources it relies on may not function anymore\n(common examples are library modules or the warnings machinery).\nThe main reason for interpreter shutdown is that the <code class=\"docutils literal notranslate\">__main__</code> module\nor the script being run has finished executing.\n</dd>\n</main>\n"}, "iterable": {"title": "iterable", "body": "<main>\n<dd>An object capable of returning its members one at a time. Examples of\niterables include all sequence types (such as <a class=\"reference internal\" href=\"library/stdtypes.html#list\" title=\"list\"><code class=\"xref py py-class docutils literal notranslate\">list</code></a>, <a class=\"reference internal\" href=\"library/stdtypes.html#str\" title=\"str\"><code class=\"xref py py-class docutils literal notranslate\">str</code></a>,\nand <a class=\"reference internal\" href=\"library/stdtypes.html#tuple\" title=\"tuple\"><code class=\"xref py py-class docutils literal notranslate\">tuple</code></a>) and some non-sequence types like <a class=\"reference internal\" href=\"library/stdtypes.html#dict\" title=\"dict\"><code class=\"xref py py-class docutils literal notranslate\">dict</code></a>,\n<a class=\"reference internal\" href=\"#term-file-object\">file objects</a>, and objects of any classes you define\nwith an <code class=\"xref py py-meth docutils literal notranslate\">__iter__()</code> method or with a <code class=\"xref py py-meth docutils literal notranslate\">__getitem__()</code> method\nthat implements <a class=\"reference internal\" href=\"#term-sequence\">Sequence</a> semantics.\nIterables can be\nused in a <a class=\"reference internal\" href=\"reference/compound_stmts.html#for\"><code class=\"xref std std-keyword docutils literal notranslate\">for</code></a> loop and in many other places where a sequence is\nneeded (<a class=\"reference internal\" href=\"library/functions.html#zip\" title=\"zip\"><code class=\"xref py py-func docutils literal notranslate\">zip()</code></a>, <a class=\"reference internal\" href=\"library/functions.html#map\" title=\"map\"><code class=\"xref py py-func docutils literal notranslate\">map()</code></a>, \u2026). When an iterable object is passed\nas an argument to the built-in function <a class=\"reference internal\" href=\"library/functions.html#iter\" title=\"iter\"><code class=\"xref py py-func docutils literal notranslate\">iter()</code></a>, it returns an\niterator for the object. This iterator is good for one pass over the set\nof values. When using iterables, it is usually not necessary to call\n<a class=\"reference internal\" href=\"library/functions.html#iter\" title=\"iter\"><code class=\"xref py py-func docutils literal notranslate\">iter()</code></a> or deal with iterator objects yourself. The <code class=\"docutils literal notranslate\">for</code>\nstatement does that automatically for you, creating a temporary unnamed\nvariable to hold the iterator for the duration of the loop. See also\n<a class=\"reference internal\" href=\"#term-iterator\">iterator</a>, <a class=\"reference internal\" href=\"#term-sequence\">sequence</a>, and <a class=\"reference internal\" href=\"#term-generator\">generator</a>.\n</dd>\n</main>\n"}, "iterator": {"title": "iterator", "body": "<main>\n<dd>An object representing a stream of data. Repeated calls to the iterator\u2019s\n<a class=\"reference internal\" href=\"library/stdtypes.html#iterator.__next__\" title=\"iterator.__next__\"><code class=\"xref py py-meth docutils literal notranslate\">__next__()</code></a> method (or passing it to the built-in function\n<a class=\"reference internal\" href=\"library/functions.html#next\" title=\"next\"><code class=\"xref py py-func docutils literal notranslate\">next()</code></a>) return successive items in the stream. When no more data\nare available a <a class=\"reference internal\" href=\"library/exceptions.html#StopIteration\" title=\"StopIteration\"><code class=\"xref py py-exc docutils literal notranslate\">StopIteration</code></a> exception is raised instead. At this\npoint, the iterator object is exhausted and any further calls to its\n<code class=\"xref py py-meth docutils literal notranslate\">__next__()</code> method just raise <a class=\"reference internal\" href=\"library/exceptions.html#StopIteration\" title=\"StopIteration\"><code class=\"xref py py-exc docutils literal notranslate\">StopIteration</code></a> again. Iterators\nare required to have an <code class=\"xref py py-meth docutils literal notranslate\">__iter__()</code> method that returns the iterator\nobject itself so every iterator is also iterable and may be used in most\nplaces where other iterables are accepted. One notable exception is code\nwhich attempts multiple iteration passes. A container object (such as a\n<a class=\"reference internal\" href=\"library/stdtypes.html#list\" title=\"list\"><code class=\"xref py py-class docutils literal notranslate\">list</code></a>) produces a fresh new iterator each time you pass it to the\n<a class=\"reference internal\" href=\"library/functions.html#iter\" title=\"iter\"><code class=\"xref py py-func docutils literal notranslate\">iter()</code></a> function or use it in a <a class=\"reference internal\" href=\"reference/compound_stmts.html#for\"><code class=\"xref std std-keyword docutils literal notranslate\">for</code></a> loop. Attempting this\nwith an iterator will just return the same exhausted iterator object used\nin the previous iteration pass, making it appear like an empty container.\nMore information can be found in <a class=\"reference internal\" href=\"library/stdtypes.html#typeiter\">Iterator Types</a>.\n<div class=\"impl-detail compound\">\nCPython implementation detail: CPython does not consistently apply the requirement that an iterator\ndefine <code class=\"xref py py-meth docutils literal notranslate\">__iter__()</code>.\n</div>\n</dd>\n</main>\n"}, "key function": {"title": "key function", "body": "<main>\n<dd>A key function or collation function is a callable that returns a value\nused for sorting or ordering. For example, <a class=\"reference internal\" href=\"library/locale.html#locale.strxfrm\" title=\"locale.strxfrm\"><code class=\"xref py py-func docutils literal notranslate\">locale.strxfrm()</code></a> is\nused to produce a sort key that is aware of locale specific sort\nconventions.\nA number of tools in Python accept key functions to control how elements\nare ordered or grouped. They include <a class=\"reference internal\" href=\"library/functions.html#min\" title=\"min\"><code class=\"xref py py-func docutils literal notranslate\">min()</code></a>, <a class=\"reference internal\" href=\"library/functions.html#max\" title=\"max\"><code class=\"xref py py-func docutils literal notranslate\">max()</code></a>,\n<a class=\"reference internal\" href=\"library/functions.html#sorted\" title=\"sorted\"><code class=\"xref py py-func docutils literal notranslate\">sorted()</code></a>, <a class=\"reference internal\" href=\"library/stdtypes.html#list.sort\" title=\"list.sort\"><code class=\"xref py py-meth docutils literal notranslate\">list.sort()</code></a>, <a class=\"reference internal\" href=\"library/heapq.html#heapq.merge\" title=\"heapq.merge\"><code class=\"xref py py-func docutils literal notranslate\">heapq.merge()</code></a>,\n<a class=\"reference internal\" href=\"library/heapq.html#heapq.nsmallest\" title=\"heapq.nsmallest\"><code class=\"xref py py-func docutils literal notranslate\">heapq.nsmallest()</code></a>, <a class=\"reference internal\" href=\"library/heapq.html#heapq.nlargest\" title=\"heapq.nlargest\"><code class=\"xref py py-func docutils literal notranslate\">heapq.nlargest()</code></a>, and\n<a class=\"reference internal\" href=\"library/itertools.html#itertools.groupby\" title=\"itertools.groupby\"><code class=\"xref py py-func docutils literal notranslate\">itertools.groupby()</code></a>.\nThere are several ways to create a key function. For example. the\n<a class=\"reference internal\" href=\"library/stdtypes.html#str.lower\" title=\"str.lower\"><code class=\"xref py py-meth docutils literal notranslate\">str.lower()</code></a> method can serve as a key function for case insensitive\nsorts. Alternatively, a key function can be built from a\n<a class=\"reference internal\" href=\"reference/expressions.html#lambda\"><code class=\"xref std std-keyword docutils literal notranslate\">lambda</code></a> expression such as <code class=\"docutils literal notranslate\">lambda r: (r[0], r[2])</code>. Also,\nthe <a class=\"reference internal\" href=\"library/operator.html#module-operator\" title=\"operator: Functions corresponding to the standard operators.\"><code class=\"xref py py-mod docutils literal notranslate\">operator</code></a> module provides three key function constructors:\n<a class=\"reference internal\" href=\"library/operator.html#operator.attrgetter\" title=\"operator.attrgetter\"><code class=\"xref py py-func docutils literal notranslate\">attrgetter()</code></a>, <a class=\"reference internal\" href=\"library/operator.html#operator.itemgetter\" title=\"operator.itemgetter\"><code class=\"xref py py-func docutils literal notranslate\">itemgetter()</code></a>, and\n<a class=\"reference internal\" href=\"library/operator.html#operator.methodcaller\" title=\"operator.methodcaller\"><code class=\"xref py py-func docutils literal notranslate\">methodcaller()</code></a>. See the <a class=\"reference internal\" href=\"howto/sorting.html#sortinghowto\">Sorting HOW TO</a> for examples of how to create and use key functions.\n</dd>\n</main>\n"}, "keyword argument": {"title": "keyword argument", "body": "<main>\n<dd>See <a class=\"reference internal\" href=\"#term-argument\">argument</a>.\n</dd>\n</main>\n"}, "lambda": {"title": "lambda", "body": "<main>\n<dd>An anonymous inline function consisting of a single <a class=\"reference internal\" href=\"#term-expression\">expression</a>\nwhich is evaluated when the function is called. The syntax to create\na lambda function is <code class=\"docutils literal notranslate\">lambda [parameters]: expression</code>\n</dd>\n</main>\n"}, "lbyl": {"title": "LBYL", "body": "<main>\n<dd>Look before you leap. This coding style explicitly tests for\npre-conditions before making calls or lookups. This style contrasts with\nthe <a class=\"reference internal\" href=\"#term-EAFP\">EAFP</a> approach and is characterized by the presence of many\n<a class=\"reference internal\" href=\"reference/compound_stmts.html#if\"><code class=\"xref std std-keyword docutils literal notranslate\">if</code></a> statements.\nIn a multi-threaded environment, the LBYL approach can risk introducing a\nrace condition between \u201cthe looking\u201d and \u201cthe leaping\u201d. For example, the\ncode, <code class=\"docutils literal notranslate\">if key in mapping: return mapping[key]</code> can fail if another\nthread removes key from mapping after the test, but before the lookup.\nThis issue can be solved with locks or by using the EAFP approach.\n</dd>\n</main>\n"}, "locale encoding": {"title": "locale encoding", "body": "<main>\n<dd>On Unix, it is the encoding of the LC_CTYPE locale. It can be set with\n<code class=\"docutils literal notranslate\">locale.setlocale(locale.LC_CTYPE, new_locale)</code>.\nOn Windows, it is the ANSI code page (ex: <code class=\"docutils literal notranslate\">cp1252</code>).\n<code class=\"docutils literal notranslate\">locale.getpreferredencoding(False)</code> can be used to get the locale\nencoding.\nPython uses the <a class=\"reference internal\" href=\"#term-filesystem-encoding-and-error-handler\">filesystem encoding and error handler</a> to convert\nbetween Unicode filenames and bytes filenames.\n</dd>\n</main>\n"}, "list": {"title": "list", "body": "<main>\n<dd>A built-in Python <a class=\"reference internal\" href=\"#term-sequence\">sequence</a>. Despite its name it is more akin\nto an array in other languages than to a linked list since access to\nelements is O(1).\n</dd>\n</main>\n"}, "list comprehension": {"title": "list comprehension", "body": "<main>\n<dd>A compact way to process all or part of the elements in a sequence and\nreturn a list with the results. <code class=\"docutils literal notranslate\">result = ['{:#04x}'.format(x) for x in\nrange(256) if x % 2 == 0]</code> generates a list of strings containing\neven hex numbers (0x..) in the range from 0 to 255. The <a class=\"reference internal\" href=\"reference/compound_stmts.html#if\"><code class=\"xref std std-keyword docutils literal notranslate\">if</code></a>\nclause is optional. If omitted, all elements in <code class=\"docutils literal notranslate\">range(256)</code> are\nprocessed.\n</dd>\n</main>\n"}, "loader": {"title": "loader", "body": "<main>\n<dd>An object that loads a module. It must define a method named\n<code class=\"xref py py-meth docutils literal notranslate\">load_module()</code>. A loader is typically returned by a\n<a class=\"reference internal\" href=\"#term-finder\">finder</a>. See <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0302\">PEP 302</a> for details and\n<a class=\"reference internal\" href=\"library/importlib.html#importlib.abc.Loader\" title=\"importlib.abc.Loader\"><code class=\"xref py py-class docutils literal notranslate\">importlib.abc.Loader</code></a> for an <a class=\"reference internal\" href=\"#term-abstract-base-class\">abstract base class</a>.\n</dd>\n</main>\n"}, "magic method": {"title": "magic method", "body": "<main>\n<dd>An informal synonym for <a class=\"reference internal\" href=\"#term-special-method\">special method</a>.\n</dd>\n</main>\n"}, "mapping": {"title": "mapping", "body": "<main>\n<dd>A container object that supports arbitrary key lookups and implements the\nmethods specified in the <a class=\"reference internal\" href=\"library/collections.abc.html#collections.abc.Mapping\" title=\"collections.abc.Mapping\"><code class=\"xref py py-class docutils literal notranslate\">Mapping</code></a> or\n<a class=\"reference internal\" href=\"library/collections.abc.html#collections.abc.MutableMapping\" title=\"collections.abc.MutableMapping\"><code class=\"xref py py-class docutils literal notranslate\">MutableMapping</code></a>\n<a class=\"reference internal\" href=\"library/collections.abc.html#collections-abstract-base-classes\">abstract base classes</a>. Examples\ninclude <a class=\"reference internal\" href=\"library/stdtypes.html#dict\" title=\"dict\"><code class=\"xref py py-class docutils literal notranslate\">dict</code></a>, <a class=\"reference internal\" href=\"library/collections.html#collections.defaultdict\" title=\"collections.defaultdict\"><code class=\"xref py py-class docutils literal notranslate\">collections.defaultdict</code></a>,\n<a class=\"reference internal\" href=\"library/collections.html#collections.OrderedDict\" title=\"collections.OrderedDict\"><code class=\"xref py py-class docutils literal notranslate\">collections.OrderedDict</code></a> and <a class=\"reference internal\" href=\"library/collections.html#collections.Counter\" title=\"collections.Counter\"><code class=\"xref py py-class docutils literal notranslate\">collections.Counter</code></a>.\n</dd>\n</main>\n"}, "meta path finder": {"title": "meta path finder", "body": "<main>\n<dd>A <a class=\"reference internal\" href=\"#term-finder\">finder</a> returned by a search of <a class=\"reference internal\" href=\"library/sys.html#sys.meta_path\" title=\"sys.meta_path\"><code class=\"xref py py-data docutils literal notranslate\">sys.meta_path</code></a>. Meta path\nfinders are related to, but different from <a class=\"reference internal\" href=\"#term-path-entry-finder\">path entry finders</a>.\nSee <a class=\"reference internal\" href=\"library/importlib.html#importlib.abc.MetaPathFinder\" title=\"importlib.abc.MetaPathFinder\"><code class=\"xref py py-class docutils literal notranslate\">importlib.abc.MetaPathFinder</code></a> for the methods that meta path\nfinders implement.\n</dd>\n</main>\n"}, "metaclass": {"title": "metaclass", "body": "<main>\n<dd>The class of a class. Class definitions create a class name, a class\ndictionary, and a list of base classes. The metaclass is responsible for\ntaking those three arguments and creating the class. Most object oriented\nprogramming languages provide a default implementation. What makes Python\nspecial is that it is possible to create custom metaclasses. Most users\nnever need this tool, but when the need arises, metaclasses can provide\npowerful, elegant solutions. They have been used for logging attribute\naccess, adding thread-safety, tracking object creation, implementing\nsingletons, and many other tasks.\nMore information can be found in <a class=\"reference internal\" href=\"reference/datamodel.html#metaclasses\">Metaclasses</a>.\n</dd>\n</main>\n"}, "method": {"title": "method", "body": "<main>\n<dd>A function which is defined inside a class body. If called as an attribute\nof an instance of that class, the method will get the instance object as\nits first <a class=\"reference internal\" href=\"#term-argument\">argument</a> (which is usually called <code class=\"docutils literal notranslate\">self</code>).\nSee <a class=\"reference internal\" href=\"#term-function\">function</a> and <a class=\"reference internal\" href=\"#term-nested-scope\">nested scope</a>.\n</dd>\n</main>\n"}, "method resolution order": {"title": "method resolution order", "body": "<main>\n<dd>Method Resolution Order is the order in which base classes are searched\nfor a member during lookup. See <a class=\"reference external\" href=\"https://www.python.org/download/releases/2.3/mro/\">The Python 2.3 Method Resolution Order</a> for details of the\nalgorithm used by the Python interpreter since the 2.3 release.\n</dd>\n</main>\n"}, "module": {"title": "module", "body": "<main>\n<dd>An object that serves as an organizational unit of Python code. Modules\nhave a namespace containing arbitrary Python objects. Modules are loaded\ninto Python by the process of <a class=\"reference internal\" href=\"#term-importing\">importing</a>.\nSee also <a class=\"reference internal\" href=\"#term-package\">package</a>.\n</dd>\n</main>\n"}, "module spec": {"title": "module spec", "body": "<main>\n<dd>A namespace containing the import-related information used to load a\nmodule. An instance of <a class=\"reference internal\" href=\"library/importlib.html#importlib.machinery.ModuleSpec\" title=\"importlib.machinery.ModuleSpec\"><code class=\"xref py py-class docutils literal notranslate\">importlib.machinery.ModuleSpec</code></a>.\n</dd>\n</main>\n"}, "mro": {"title": "MRO", "body": "<main>\n<dd>See <a class=\"reference internal\" href=\"#term-method-resolution-order\">method resolution order</a>.\n</dd>\n</main>\n"}, "mutable": {"title": "mutable", "body": "<main>\n<dd>Mutable objects can change their value but keep their <a class=\"reference internal\" href=\"library/functions.html#id\" title=\"id\"><code class=\"xref py py-func docutils literal notranslate\">id()</code></a>. See\nalso <a class=\"reference internal\" href=\"#term-immutable\">immutable</a>.\n</dd>\n</main>\n"}, "named tuple": {"title": "named tuple", "body": "<main>\n<dd>The term \u201cnamed tuple\u201d applies to any type or class that inherits from\ntuple and whose indexable elements are also accessible using named\nattributes. The type or class may have other features as well.\nSeveral built-in types are named tuples, including the values returned\nby <a class=\"reference internal\" href=\"library/time.html#time.localtime\" title=\"time.localtime\"><code class=\"xref py py-func docutils literal notranslate\">time.localtime()</code></a> and <a class=\"reference internal\" href=\"library/os.html#os.stat\" title=\"os.stat\"><code class=\"xref py py-func docutils literal notranslate\">os.stat()</code></a>. Another example is\n<a class=\"reference internal\" href=\"library/sys.html#sys.float_info\" title=\"sys.float_info\"><code class=\"xref py py-data docutils literal notranslate\">sys.float_info</code></a>:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>&gt;&gt;&gt; sys.float_info[1] # indexed access\n1024\n&gt;&gt;&gt; sys.float_info.max_exp # named field access\n1024\n&gt;&gt;&gt; isinstance(sys.float_info, tuple) # kind of tuple\nTrue\n</pre></div>\n</div>\nSome named tuples are built-in types (such as the above examples).\nAlternatively, a named tuple can be created from a regular class\ndefinition that inherits from <a class=\"reference internal\" href=\"library/stdtypes.html#tuple\" title=\"tuple\"><code class=\"xref py py-class docutils literal notranslate\">tuple</code></a> and that defines named\nfields. Such a class can be written by hand or it can be created with\nthe factory function <a class=\"reference internal\" href=\"library/collections.html#collections.namedtuple\" title=\"collections.namedtuple\"><code class=\"xref py py-func docutils literal notranslate\">collections.namedtuple()</code></a>. The latter\ntechnique also adds some extra methods that may not be found in\nhand-written or built-in named tuples.\n</dd>\n</main>\n"}, "namespace": {"title": "namespace", "body": "<main>\n<dd>The place where a variable is stored. Namespaces are implemented as\ndictionaries. There are the local, global and built-in namespaces as well\nas nested namespaces in objects (in methods). Namespaces support\nmodularity by preventing naming conflicts. For instance, the functions\n<a class=\"reference internal\" href=\"library/functions.html#open\" title=\"open\"><code class=\"xref py py-func docutils literal notranslate\">builtins.open</code></a> and <a class=\"reference internal\" href=\"library/os.html#os.open\" title=\"os.open\"><code class=\"xref py py-func docutils literal notranslate\">os.open()</code></a> are distinguished by\ntheir namespaces. Namespaces also aid readability and maintainability by\nmaking it clear which module implements a function. For instance, writing\n<a class=\"reference internal\" href=\"library/random.html#random.seed\" title=\"random.seed\"><code class=\"xref py py-func docutils literal notranslate\">random.seed()</code></a> or <a class=\"reference internal\" href=\"library/itertools.html#itertools.islice\" title=\"itertools.islice\"><code class=\"xref py py-func docutils literal notranslate\">itertools.islice()</code></a> makes it clear that those\nfunctions are implemented by the <a class=\"reference internal\" href=\"library/random.html#module-random\" title=\"random: Generate pseudo-random numbers with various common distributions.\"><code class=\"xref py py-mod docutils literal notranslate\">random</code></a> and <a class=\"reference internal\" href=\"library/itertools.html#module-itertools\" title=\"itertools: Functions creating iterators for efficient looping.\"><code class=\"xref py py-mod docutils literal notranslate\">itertools</code></a>\nmodules, respectively.\n</dd>\n</main>\n"}, "namespace package": {"title": "namespace package", "body": "<main>\n<dd>A <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0420\">PEP 420</a> <a class=\"reference internal\" href=\"#term-package\">package</a> which serves only as a container for\nsubpackages. Namespace packages may have no physical representation,\nand specifically are not like a <a class=\"reference internal\" href=\"#term-regular-package\">regular package</a> because they\nhave no <code class=\"docutils literal notranslate\">__init__.py</code> file.\nSee also <a class=\"reference internal\" href=\"#term-module\">module</a>.\n</dd>\n</main>\n"}, "nested scope": {"title": "nested scope", "body": "<main>\n<dd>The ability to refer to a variable in an enclosing definition. For\ninstance, a function defined inside another function can refer to\nvariables in the outer function. Note that nested scopes by default work\nonly for reference and not for assignment. Local variables both read and\nwrite in the innermost scope. Likewise, global variables read and write\nto the global namespace. The <a class=\"reference internal\" href=\"reference/simple_stmts.html#nonlocal\"><code class=\"xref std std-keyword docutils literal notranslate\">nonlocal</code></a> allows writing to outer\nscopes.\n</dd>\n</main>\n"}, "new-style class": {"title": "new-style class", "body": "<main>\n<dd>Old name for the flavor of classes now used for all class objects. In\nearlier Python versions, only new-style classes could use Python\u2019s newer,\nversatile features like <a class=\"reference internal\" href=\"reference/datamodel.html#object.__slots__\" title=\"object.__slots__\"><code class=\"xref py py-attr docutils literal notranslate\">__slots__</code></a>, descriptors,\nproperties, <code class=\"xref py py-meth docutils literal notranslate\">__getattribute__()</code>, class methods, and static methods.\n</dd>\n</main>\n"}, "object": {"title": "object", "body": "<main>\n<dd>Any data with state (attributes or value) and defined behavior\n(methods). Also the ultimate base class of any <a class=\"reference internal\" href=\"#term-new-style-class\">new-style\nclass</a>.\n</dd>\n</main>\n"}, "package": {"title": "package", "body": "<main>\n<dd>A Python <a class=\"reference internal\" href=\"#term-module\">module</a> which can contain submodules or recursively,\nsubpackages. Technically, a package is a Python module with a\n<code class=\"docutils literal notranslate\">__path__</code> attribute.\nSee also <a class=\"reference internal\" href=\"#term-regular-package\">regular package</a> and <a class=\"reference internal\" href=\"#term-namespace-package\">namespace package</a>.\n</dd>\n</main>\n"}, "parameter": {"title": "parameter", "body": "<main>\n<dd>A named entity in a <a class=\"reference internal\" href=\"#term-function\">function</a> (or method) definition that\nspecifies an <a class=\"reference internal\" href=\"#term-argument\">argument</a> (or in some cases, arguments) that the\nfunction can accept. There are five kinds of parameter:\n<ul>\n<li>positional-or-keyword: specifies an argument that can be passed\neither <a class=\"reference internal\" href=\"#term-argument\">positionally</a> or as a <a class=\"reference internal\" href=\"#term-argument\">keyword argument</a>. This is the default kind of parameter, for example foo\nand bar in the following:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>def func(foo, bar=None): ...\n</pre></div>\n</div>\n</li>\n</ul>\n<ul id=\"positional-only-parameter\">\n<li>positional-only: specifies an argument that can be supplied only\nby position. Positional-only parameters can be defined by including a\n<code class=\"docutils literal notranslate\">/</code> character in the parameter list of the function definition after\nthem, for example posonly1 and posonly2 in the following:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>def func(posonly1, posonly2, /, positional_or_keyword): ...\n</pre></div>\n</div>\n</li>\n</ul>\n<ul id=\"keyword-only-parameter\">\n<li>keyword-only: specifies an argument that can be supplied only\nby keyword. Keyword-only parameters can be defined by including a\nsingle var-positional parameter or bare <code class=\"docutils literal notranslate\">*</code> in the parameter list\nof the function definition before them, for example kw_only1 and\nkw_only2 in the following:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>def func(arg, *, kw_only1, kw_only2): ...\n</pre></div>\n</div>\n</li>\n<li>var-positional: specifies that an arbitrary sequence of\npositional arguments can be provided (in addition to any positional\narguments already accepted by other parameters). Such a parameter can\nbe defined by prepending the parameter name with <code class=\"docutils literal notranslate\">*</code>, for example\nargs in the following:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>def func(*args, **kwargs): ...\n</pre></div>\n</div>\n</li>\n<li>var-keyword: specifies that arbitrarily many keyword arguments\ncan be provided (in addition to any keyword arguments already accepted\nby other parameters). Such a parameter can be defined by prepending\nthe parameter name with <code class=\"docutils literal notranslate\">**</code>, for example kwargs in the example\nabove.</li>\n</ul>\nParameters can specify both optional and required arguments, as well as\ndefault values for some optional arguments.\nSee also the <a class=\"reference internal\" href=\"#term-argument\">argument</a> glossary entry, the FAQ question on\n<a class=\"reference internal\" href=\"faq/programming.html#faq-argument-vs-parameter\">the difference between arguments and parameters</a>, the <a class=\"reference internal\" href=\"library/inspect.html#inspect.Parameter\" title=\"inspect.Parameter\"><code class=\"xref py py-class docutils literal notranslate\">inspect.Parameter</code></a> class, the\n<a class=\"reference internal\" href=\"reference/compound_stmts.html#function\">Function definitions</a> section, and <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0362\">PEP 362</a>.\n</dd>\n</main>\n"}, "path entry": {"title": "path entry", "body": "<main>\n<dd>A single location on the <a class=\"reference internal\" href=\"#term-import-path\">import path</a> which the <a class=\"reference internal\" href=\"#term-path-based-finder\">path\nbased finder</a> consults to find modules for importing.\n</dd>\n</main>\n"}, "path entry finder": {"title": "path entry finder", "body": "<main>\n<dd>A <a class=\"reference internal\" href=\"#term-finder\">finder</a> returned by a callable on <a class=\"reference internal\" href=\"library/sys.html#sys.path_hooks\" title=\"sys.path_hooks\"><code class=\"xref py py-data docutils literal notranslate\">sys.path_hooks</code></a>\n(i.e. a <a class=\"reference internal\" href=\"#term-path-entry-hook\">path entry hook</a>) which knows how to locate modules given\na <a class=\"reference internal\" href=\"#term-path-entry\">path entry</a>.\nSee <a class=\"reference internal\" href=\"library/importlib.html#importlib.abc.PathEntryFinder\" title=\"importlib.abc.PathEntryFinder\"><code class=\"xref py py-class docutils literal notranslate\">importlib.abc.PathEntryFinder</code></a> for the methods that path entry\nfinders implement.\n</dd>\n</main>\n"}, "path entry hook": {"title": "path entry hook", "body": "<main>\n<dd>A callable on the <code class=\"xref py py-data docutils literal notranslate\">sys.path_hook</code> list which returns a <a class=\"reference internal\" href=\"#term-path-entry-finder\">path\nentry finder</a> if it knows how to find modules on a specific <a class=\"reference internal\" href=\"#term-path-entry\">path\nentry</a>.\n</dd>\n</main>\n"}, "path based finder": {"title": "path based finder", "body": "<main>\n<dd>One of the default <a class=\"reference internal\" href=\"#term-meta-path-finder\">meta path finders</a> which\nsearches an <a class=\"reference internal\" href=\"#term-import-path\">import path</a> for modules.\n</dd>\n</main>\n"}, "path-like object": {"title": "path-like object", "body": "<main>\n<dd>An object representing a file system path. A path-like object is either\na <a class=\"reference internal\" href=\"library/stdtypes.html#str\" title=\"str\"><code class=\"xref py py-class docutils literal notranslate\">str</code></a> or <a class=\"reference internal\" href=\"library/stdtypes.html#bytes\" title=\"bytes\"><code class=\"xref py py-class docutils literal notranslate\">bytes</code></a> object representing a path, or an object\nimplementing the <a class=\"reference internal\" href=\"library/os.html#os.PathLike\" title=\"os.PathLike\"><code class=\"xref py py-class docutils literal notranslate\">os.PathLike</code></a> protocol. An object that supports\nthe <a class=\"reference internal\" href=\"library/os.html#os.PathLike\" title=\"os.PathLike\"><code class=\"xref py py-class docutils literal notranslate\">os.PathLike</code></a> protocol can be converted to a <a class=\"reference internal\" href=\"library/stdtypes.html#str\" title=\"str\"><code class=\"xref py py-class docutils literal notranslate\">str</code></a> or\n<a class=\"reference internal\" href=\"library/stdtypes.html#bytes\" title=\"bytes\"><code class=\"xref py py-class docutils literal notranslate\">bytes</code></a> file system path by calling the <a class=\"reference internal\" href=\"library/os.html#os.fspath\" title=\"os.fspath\"><code class=\"xref py py-func docutils literal notranslate\">os.fspath()</code></a> function;\n<a class=\"reference internal\" href=\"library/os.html#os.fsdecode\" title=\"os.fsdecode\"><code class=\"xref py py-func docutils literal notranslate\">os.fsdecode()</code></a> and <a class=\"reference internal\" href=\"library/os.html#os.fsencode\" title=\"os.fsencode\"><code class=\"xref py py-func docutils literal notranslate\">os.fsencode()</code></a> can be used to guarantee a\n<a class=\"reference internal\" href=\"library/stdtypes.html#str\" title=\"str\"><code class=\"xref py py-class docutils literal notranslate\">str</code></a> or <a class=\"reference internal\" href=\"library/stdtypes.html#bytes\" title=\"bytes\"><code class=\"xref py py-class docutils literal notranslate\">bytes</code></a> result instead, respectively. Introduced\nby <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0519\">PEP 519</a>.\n</dd>\n</main>\n"}, "pep": {"title": "PEP", "body": "<main>\n<dd>Python Enhancement Proposal. A PEP is a design document\nproviding information to the Python community, or describing a new\nfeature for Python or its processes or environment. PEPs should\nprovide a concise technical specification and a rationale for proposed\nfeatures.\nPEPs are intended to be the primary mechanisms for proposing major new\nfeatures, for collecting community input on an issue, and for documenting\nthe design decisions that have gone into Python. The PEP author is\nresponsible for building consensus within the community and documenting\ndissenting opinions.\nSee <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0001\">PEP 1</a>.\n</dd>\n</main>\n"}, "portion": {"title": "portion", "body": "<main>\n<dd>A set of files in a single directory (possibly stored in a zip file)\nthat contribute to a namespace package, as defined in <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0420\">PEP 420</a>.\n</dd>\n</main>\n"}, "positional argument": {"title": "positional argument", "body": "<main>\n<dd>See <a class=\"reference internal\" href=\"#term-argument\">argument</a>.\n</dd>\n</main>\n"}, "provisional api": {"title": "provisional API", "body": "<main>\n<dd>A provisional API is one which has been deliberately excluded from\nthe standard library\u2019s backwards compatibility guarantees. While major\nchanges to such interfaces are not expected, as long as they are marked\nprovisional, backwards incompatible changes (up to and including removal\nof the interface) may occur if deemed necessary by core developers. Such\nchanges will not be made gratuitously \u2013 they will occur only if serious\nfundamental flaws are uncovered that were missed prior to the inclusion\nof the API.\nEven for provisional APIs, backwards incompatible changes are seen as\na \u201csolution of last resort\u201d - every attempt will still be made to find\na backwards compatible resolution to any identified problems.\nThis process allows the standard library to continue to evolve over\ntime, without locking in problematic design errors for extended periods\nof time. See <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0411\">PEP 411</a> for more details.\n</dd>\n</main>\n"}, "provisional package": {"title": "provisional package", "body": "<main>\n<dd>See <a class=\"reference internal\" href=\"#term-provisional-API\">provisional API</a>.\n</dd>\n</main>\n"}, "python 3000": {"title": "Python 3000", "body": "<main>\n<dd>Nickname for the Python 3.x release line (coined long ago when the\nrelease of version 3 was something in the distant future.) This is also\nabbreviated \u201cPy3k\u201d.\n</dd>\n</main>\n"}, "pythonic": {"title": "Pythonic", "body": "<main>\n<dd>An idea or piece of code which closely follows the most common idioms\nof the Python language, rather than implementing code using concepts\ncommon to other languages. For example, a common idiom in Python is\nto loop over all elements of an iterable using a <a class=\"reference internal\" href=\"reference/compound_stmts.html#for\"><code class=\"xref std std-keyword docutils literal notranslate\">for</code></a>\nstatement. Many other languages don\u2019t have this type of construct, so\npeople unfamiliar with Python sometimes use a numerical counter instead:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>for i in range(len(food)):\n print(food[i])\n</pre></div>\n</div>\nAs opposed to the cleaner, Pythonic method:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>for piece in food:\n print(piece)\n</pre></div>\n</div>\n</dd>\n</main>\n"}, "qualified name": {"title": "qualified name", "body": "<main>\n<dd>A dotted name showing the \u201cpath\u201d from a module\u2019s global scope to a\nclass, function or method defined in that module, as defined in\n<a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-3155\">PEP 3155</a>. For top-level functions and classes, the qualified name\nis the same as the object\u2019s name:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>&gt;&gt;&gt; class C:\n... class D:\n... def meth(self):\n... pass\n...\n&gt;&gt;&gt; C.__qualname__\n&#39;C&#39;\n&gt;&gt;&gt; C.D.__qualname__\n&#39;C.D&#39;\n&gt;&gt;&gt; C.D.meth.__qualname__\n&#39;C.D.meth&#39;\n</pre></div>\n</div>\nWhen used to refer to modules, the fully qualified name means the\nentire dotted path to the module, including any parent packages,\ne.g. <code class=\"docutils literal notranslate\">email.mime.text</code>:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>&gt;&gt;&gt; import email.mime.text\n&gt;&gt;&gt; email.mime.text.__name__\n&#39;email.mime.text&#39;\n</pre></div>\n</div>\n</dd>\n</main>\n"}, "reference count": {"title": "reference count", "body": "<main>\n<dd>The number of references to an object. When the reference count of an\nobject drops to zero, it is deallocated. Reference counting is\ngenerally not visible to Python code, but it is a key element of the\n<a class=\"reference internal\" href=\"#term-CPython\">CPython</a> implementation. The <a class=\"reference internal\" href=\"library/sys.html#module-sys\" title=\"sys: Access system-specific parameters and functions.\"><code class=\"xref py py-mod docutils literal notranslate\">sys</code></a> module defines a\n<a class=\"reference internal\" href=\"library/sys.html#sys.getrefcount\" title=\"sys.getrefcount\"><code class=\"xref py py-func docutils literal notranslate\">getrefcount()</code></a> function that programmers can call to return the\nreference count for a particular object.\n</dd>\n</main>\n"}, "regular package": {"title": "regular package", "body": "<main>\n<dd>A traditional <a class=\"reference internal\" href=\"#term-package\">package</a>, such as a directory containing an\n<code class=\"docutils literal notranslate\">__init__.py</code> file.\nSee also <a class=\"reference internal\" href=\"#term-namespace-package\">namespace package</a>.\n</dd>\n</main>\n"}, "__slots__": {"title": "__slots__", "body": "<main>\n<dd>A declaration inside a class that saves memory by pre-declaring space for\ninstance attributes and eliminating instance dictionaries. Though\npopular, the technique is somewhat tricky to get right and is best\nreserved for rare cases where there are large numbers of instances in a\nmemory-critical application.\n</dd>\n</main>\n"}, "sequence": {"title": "sequence", "body": "<main>\n<dd>An <a class=\"reference internal\" href=\"#term-iterable\">iterable</a> which supports efficient element access using integer\nindices via the <code class=\"xref py py-meth docutils literal notranslate\">__getitem__()</code> special method and defines a\n<code class=\"xref py py-meth docutils literal notranslate\">__len__()</code> method that returns the length of the sequence.\nSome built-in sequence types are <a class=\"reference internal\" href=\"library/stdtypes.html#list\" title=\"list\"><code class=\"xref py py-class docutils literal notranslate\">list</code></a>, <a class=\"reference internal\" href=\"library/stdtypes.html#str\" title=\"str\"><code class=\"xref py py-class docutils literal notranslate\">str</code></a>,\n<a class=\"reference internal\" href=\"library/stdtypes.html#tuple\" title=\"tuple\"><code class=\"xref py py-class docutils literal notranslate\">tuple</code></a>, and <a class=\"reference internal\" href=\"library/stdtypes.html#bytes\" title=\"bytes\"><code class=\"xref py py-class docutils literal notranslate\">bytes</code></a>. Note that <a class=\"reference internal\" href=\"library/stdtypes.html#dict\" title=\"dict\"><code class=\"xref py py-class docutils literal notranslate\">dict</code></a> also\nsupports <code class=\"xref py py-meth docutils literal notranslate\">__getitem__()</code> and <code class=\"xref py py-meth docutils literal notranslate\">__len__()</code>, but is considered a\nmapping rather than a sequence because the lookups use arbitrary\n<a class=\"reference internal\" href=\"#term-immutable\">immutable</a> keys rather than integers.\nThe <a class=\"reference internal\" href=\"library/collections.abc.html#collections.abc.Sequence\" title=\"collections.abc.Sequence\"><code class=\"xref py py-class docutils literal notranslate\">collections.abc.Sequence</code></a> abstract base class\ndefines a much richer interface that goes beyond just\n<code class=\"xref py py-meth docutils literal notranslate\">__getitem__()</code> and <code class=\"xref py py-meth docutils literal notranslate\">__len__()</code>, adding <code class=\"xref py py-meth docutils literal notranslate\">count()</code>,\n<code class=\"xref py py-meth docutils literal notranslate\">index()</code>, <code class=\"xref py py-meth docutils literal notranslate\">__contains__()</code>, and\n<code class=\"xref py py-meth docutils literal notranslate\">__reversed__()</code>. Types that implement this expanded\ninterface can be registered explicitly using\n<a class=\"reference internal\" href=\"library/abc.html#abc.ABCMeta.register\" title=\"abc.ABCMeta.register\"><code class=\"xref py py-func docutils literal notranslate\">register()</code></a>.\n</dd>\n</main>\n"}, "set comprehension": {"title": "set comprehension", "body": "<main>\n<dd>A compact way to process all or part of the elements in an iterable and\nreturn a set with the results. <code class=\"docutils literal notranslate\">results = {c for c in 'abracadabra' if\nc not in 'abc'}</code> generates the set of strings <code class=\"docutils literal notranslate\">{'r', 'd'}</code>. See\n<a class=\"reference internal\" href=\"reference/expressions.html#comprehensions\">Displays for lists, sets and dictionaries</a>.\n</dd>\n</main>\n"}, "single dispatch": {"title": "single dispatch", "body": "<main>\n<dd>A form of <a class=\"reference internal\" href=\"#term-generic-function\">generic function</a> dispatch where the implementation is\nchosen based on the type of a single argument.\n</dd>\n</main>\n"}, "slice": {"title": "slice", "body": "<main>\n<dd>An object usually containing a portion of a <a class=\"reference internal\" href=\"#term-sequence\">sequence</a>. A slice is\ncreated using the subscript notation, <code class=\"docutils literal notranslate\">[]</code> with colons between numbers\nwhen several are given, such as in <code class=\"docutils literal notranslate\">variable_name[1:3:5]</code>. The bracket\n(subscript) notation uses <a class=\"reference internal\" href=\"library/functions.html#slice\" title=\"slice\"><code class=\"xref py py-class docutils literal notranslate\">slice</code></a> objects internally.\n</dd>\n</main>\n"}, "special method": {"title": "special method", "body": "<main>\n<dd>A method that is called implicitly by Python to execute a certain\noperation on a type, such as addition. Such methods have names starting\nand ending with double underscores. Special methods are documented in\n<a class=\"reference internal\" href=\"reference/datamodel.html#specialnames\">Special method names</a>.\n</dd>\n</main>\n"}, "statement": {"title": "statement", "body": "<main>\n<dd>A statement is part of a suite (a \u201cblock\u201d of code). A statement is either\nan <a class=\"reference internal\" href=\"#term-expression\">expression</a> or one of several constructs with a keyword, such\nas <a class=\"reference internal\" href=\"reference/compound_stmts.html#if\"><code class=\"xref std std-keyword docutils literal notranslate\">if</code></a>, <a class=\"reference internal\" href=\"reference/compound_stmts.html#while\"><code class=\"xref std std-keyword docutils literal notranslate\">while</code></a> or <a class=\"reference internal\" href=\"reference/compound_stmts.html#for\"><code class=\"xref std std-keyword docutils literal notranslate\">for</code></a>.\n</dd>\n</main>\n"}, "strong reference": {"title": "strong reference", "body": "<main>\n<dd>In Python\u2019s C API, a strong reference is a reference to an object\nwhich increments the object\u2019s reference count when it is created and\ndecrements the object\u2019s reference count when it is deleted.\nThe <a class=\"reference internal\" href=\"c-api/refcounting.html#c.Py_NewRef\" title=\"Py_NewRef\"><code class=\"xref c c-func docutils literal notranslate\">Py_NewRef()</code></a> function can be used to create a strong reference\nto an object. Usually, the <a class=\"reference internal\" href=\"c-api/refcounting.html#c.Py_DECREF\" title=\"Py_DECREF\"><code class=\"xref c c-func docutils literal notranslate\">Py_DECREF()</code></a> function must be called on\nthe strong reference before exiting the scope of the strong reference, to\navoid leaking one reference.\nSee also <a class=\"reference internal\" href=\"#term-borrowed-reference\">borrowed reference</a>.\n</dd>\n</main>\n"}, "text encoding": {"title": "text encoding", "body": "<main>\n<dd>A string in Python is a sequence of Unicode code points (in range\n<code class=\"docutils literal notranslate\">U+0000</code>\u2013<code class=\"docutils literal notranslate\">U+10FFFF</code>). To store or transfer a string, it needs to be\nserialized as a sequence of bytes.\nSerializing a string into a sequence of bytes is known as \u201cencoding\u201d, and\nrecreating the string from the sequence of bytes is known as \u201cdecoding\u201d.\nThere are a variety of different text serialization\n<a class=\"reference internal\" href=\"library/codecs.html#standard-encodings\">codecs</a>, which are collectively referred to as\n\u201ctext encodings\u201d.\n</dd>\n</main>\n"}, "text file": {"title": "text file", "body": "<main>\n<dd>A <a class=\"reference internal\" href=\"#term-file-object\">file object</a> able to read and write <a class=\"reference internal\" href=\"library/stdtypes.html#str\" title=\"str\"><code class=\"xref py py-class docutils literal notranslate\">str</code></a> objects.\nOften, a text file actually accesses a byte-oriented datastream\nand handles the <a class=\"reference internal\" href=\"#term-text-encoding\">text encoding</a> automatically.\nExamples of text files are files opened in text mode (<code class=\"docutils literal notranslate\">'r'</code> or <code class=\"docutils literal notranslate\">'w'</code>),\n<a class=\"reference internal\" href=\"library/sys.html#sys.stdin\" title=\"sys.stdin\"><code class=\"xref py py-data docutils literal notranslate\">sys.stdin</code></a>, <a class=\"reference internal\" href=\"library/sys.html#sys.stdout\" title=\"sys.stdout\"><code class=\"xref py py-data docutils literal notranslate\">sys.stdout</code></a>, and instances of\n<a class=\"reference internal\" href=\"library/io.html#io.StringIO\" title=\"io.StringIO\"><code class=\"xref py py-class docutils literal notranslate\">io.StringIO</code></a>.\nSee also <a class=\"reference internal\" href=\"#term-binary-file\">binary file</a> for a file object able to read and write\n<a class=\"reference internal\" href=\"#term-bytes-like-object\">bytes-like objects</a>.\n</dd>\n</main>\n"}, "triple-quoted string": {"title": "triple-quoted string", "body": "<main>\n<dd>A string which is bound by three instances of either a quotation mark\n(\u201d) or an apostrophe (\u2018). While they don\u2019t provide any functionality\nnot available with single-quoted strings, they are useful for a number\nof reasons. They allow you to include unescaped single and double\nquotes within a string and they can span multiple lines without the\nuse of the continuation character, making them especially useful when\nwriting docstrings.\n</dd>\n</main>\n"}, "type": {"title": "type", "body": "<main>\n<dd>The type of a Python object determines what kind of object it is; every\nobject has a type. An object\u2019s type is accessible as its\n<a class=\"reference internal\" href=\"library/stdtypes.html#instance.__class__\" title=\"instance.__class__\"><code class=\"xref py py-attr docutils literal notranslate\">__class__</code></a> attribute or can be retrieved with\n<code class=\"docutils literal notranslate\">type(obj)</code>.\n</dd>\n</main>\n"}, "type alias": {"title": "type alias", "body": "<main>\n<dd>A synonym for a type, created by assigning the type to an identifier.\nType aliases are useful for simplifying <a class=\"reference internal\" href=\"#term-type-hint\">type hints</a>.\nFor example:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>def remove_gray_shades(\n colors: list[tuple[int, int, int]]) -&gt; list[tuple[int, int, int]]:\n pass\n</pre></div>\n</div>\ncould be made more readable like this:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>Color = tuple[int, int, int]\n\ndef remove_gray_shades(colors: list[Color]) -&gt; list[Color]:\n pass\n</pre></div>\n</div>\nSee <a class=\"reference internal\" href=\"library/typing.html#module-typing\" title=\"typing: Support for type hints (see :pep:`484`).\"><code class=\"xref py py-mod docutils literal notranslate\">typing</code></a> and <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0484\">PEP 484</a>, which describe this functionality.\n</dd>\n</main>\n"}, "type hint": {"title": "type hint", "body": "<main>\n<dd>An <a class=\"reference internal\" href=\"#term-annotation\">annotation</a> that specifies the expected type for a variable, a class\nattribute, or a function parameter or return value.\nType hints are optional and are not enforced by Python but\nthey are useful to static type analysis tools, and aid IDEs with code\ncompletion and refactoring.\nType hints of global variables, class attributes, and functions,\nbut not local variables, can be accessed using\n<a class=\"reference internal\" href=\"library/typing.html#typing.get_type_hints\" title=\"typing.get_type_hints\"><code class=\"xref py py-func docutils literal notranslate\">typing.get_type_hints()</code></a>.\nSee <a class=\"reference internal\" href=\"library/typing.html#module-typing\" title=\"typing: Support for type hints (see :pep:`484`).\"><code class=\"xref py py-mod docutils literal notranslate\">typing</code></a> and <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0484\">PEP 484</a>, which describe this functionality.\n</dd>\n</main>\n"}, "universal newlines": {"title": "universal newlines", "body": "<main>\n<dd>A manner of interpreting text streams in which all of the following are\nrecognized as ending a line: the Unix end-of-line convention <code class=\"docutils literal notranslate\">'\\n'</code>,\nthe Windows convention <code class=\"docutils literal notranslate\">'\\r\\n'</code>, and the old Macintosh convention\n<code class=\"docutils literal notranslate\">'\\r'</code>. See <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0278\">PEP 278</a> and <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-3116\">PEP 3116</a>, as well as\n<a class=\"reference internal\" href=\"library/stdtypes.html#bytes.splitlines\" title=\"bytes.splitlines\"><code class=\"xref py py-func docutils literal notranslate\">bytes.splitlines()</code></a> for an additional use.\n</dd>\n</main>\n"}, "variable annotation": {"title": "variable annotation", "body": "<main>\n<dd>An <a class=\"reference internal\" href=\"#term-annotation\">annotation</a> of a variable or a class attribute.\nWhen annotating a variable or a class attribute, assignment is optional:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>class C:\n field: &#39;annotation&#39;\n</pre></div>\n</div>\nVariable annotations are usually used for\n<a class=\"reference internal\" href=\"#term-type-hint\">type hints</a>: for example this variable is expected to take\n<a class=\"reference internal\" href=\"library/functions.html#int\" title=\"int\"><code class=\"xref py py-class docutils literal notranslate\">int</code></a> values:\n<div class=\"highlight-python3 notranslate\"><div class=\"highlight\"><pre>count: int = 0\n</pre></div>\n</div>\nVariable annotation syntax is explained in section <a class=\"reference internal\" href=\"reference/simple_stmts.html#annassign\">Annotated assignment statements</a>.\nSee <a class=\"reference internal\" href=\"#term-function-annotation\">function annotation</a>, <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0484\">PEP 484</a>\nand <a class=\"pep reference external\" href=\"https://www.python.org/dev/peps/pep-0526\">PEP 526</a>, which describe this functionality.\nAlso see <a class=\"reference internal\" href=\"howto/annotations.html#annotations-howto\">Annotations Best Practices</a>\nfor best practices on working with annotations.\n</dd>\n</main>\n"}, "virtual environment": {"title": "virtual environment", "body": "<main>\n<dd>A cooperatively isolated runtime environment that allows Python users\nand applications to install and upgrade Python distribution packages\nwithout interfering with the behaviour of other Python applications\nrunning on the same system.\nSee also <a class=\"reference internal\" href=\"library/venv.html#module-venv\" title=\"venv: Creation of virtual environments.\"><code class=\"xref py py-mod docutils literal notranslate\">venv</code></a>.\n</dd>\n</main>\n"}, "virtual machine": {"title": "virtual machine", "body": "<main>\n<dd>A computer defined entirely in software. Python\u2019s virtual machine\nexecutes the <a class=\"reference internal\" href=\"#term-bytecode\">bytecode</a> emitted by the bytecode compiler.\n</dd>\n</main>\n"}, "zen of python": {"title": "Zen of Python", "body": "<main>\n<dd>Listing of Python design principles and philosophies that are helpful in\nunderstanding and using the language. The listing can be found by typing\n\u201c<code class=\"docutils literal notranslate\">import this</code>\u201d at the interactive prompt.\n</dd>\n</main>\n"}}

${this.title}

Code Editor : glossary.json