forked from AFPy/python-docs-fr
1703 lines
55 KiB
Plaintext
1703 lines
55 KiB
Plaintext
|
# SOME DESCRIPTIVE TITLE.
|
|||
|
# Copyright (C) 2001-2016, Python Software Foundation
|
|||
|
# This file is distributed under the same license as the Python package.
|
|||
|
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
|||
|
#
|
|||
|
#, fuzzy
|
|||
|
msgid ""
|
|||
|
msgstr ""
|
|||
|
"Project-Id-Version: Python 3.6\n"
|
|||
|
"Report-Msgid-Bugs-To: \n"
|
|||
|
"POT-Creation-Date: 2016-10-17 21:44+0200\n"
|
|||
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
|||
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
|||
|
"Language-Team: LANGUAGE <LL@li.org>\n"
|
|||
|
"MIME-Version: 1.0\n"
|
|||
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|||
|
"Content-Transfer-Encoding: 8bit\n"
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:5
|
|||
|
msgid "Glossary"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:10
|
|||
|
msgid ">>>"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:12
|
|||
|
msgid ""
|
|||
|
"The default Python prompt of the interactive shell. Often seen for code "
|
|||
|
"examples which can be executed interactively in the interpreter."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:14
|
|||
|
msgid "..."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:16
|
|||
|
msgid ""
|
|||
|
"The default Python prompt of the interactive shell when entering code for an "
|
|||
|
"indented code block or within a pair of matching left and right delimiters "
|
|||
|
"(parentheses, square brackets or curly braces)."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:19
|
|||
|
msgid "2to3"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:21
|
|||
|
msgid ""
|
|||
|
"A tool that tries to convert Python 2.x code to Python 3.x code by handling "
|
|||
|
"most of the incompatibilities which can be detected by parsing the source "
|
|||
|
"and traversing the parse tree."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:25
|
|||
|
msgid ""
|
|||
|
"2to3 is available in the standard library as :mod:`lib2to3`; a standalone "
|
|||
|
"entry point is provided as :file:`Tools/scripts/2to3`. See :ref:`2to3-"
|
|||
|
"reference`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:28
|
|||
|
msgid "abstract base class"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:30
|
|||
|
msgid ""
|
|||
|
"Abstract base classes complement :term:`duck-typing` by providing a way to "
|
|||
|
"define interfaces when other techniques like :func:`hasattr` would be clumsy "
|
|||
|
"or subtly wrong (for example with :ref:`magic methods <special-lookup>`). "
|
|||
|
"ABCs introduce virtual subclasses, which are classes that don't inherit from "
|
|||
|
"a class but are still recognized by :func:`isinstance` and :func:"
|
|||
|
"`issubclass`; see the :mod:`abc` module documentation. Python comes with "
|
|||
|
"many built-in ABCs for data structures (in the :mod:`collections.abc` "
|
|||
|
"module), numbers (in the :mod:`numbers` module), streams (in the :mod:`io` "
|
|||
|
"module), import finders and loaders (in the :mod:`importlib.abc` module). "
|
|||
|
"You can create your own ABCs with the :mod:`abc` module."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:41
|
|||
|
msgid "argument"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:43
|
|||
|
msgid ""
|
|||
|
"A value passed to a :term:`function` (or :term:`method`) when calling the "
|
|||
|
"function. There are two kinds of argument:"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:46
|
|||
|
msgid ""
|
|||
|
":dfn:`keyword argument`: an argument preceded by an identifier (e.g. "
|
|||
|
"``name=``) in a function call or passed as a value in a dictionary preceded "
|
|||
|
"by ``**``. For example, ``3`` and ``5`` are both keyword arguments in the "
|
|||
|
"following calls to :func:`complex`::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:54
|
|||
|
msgid ""
|
|||
|
":dfn:`positional argument`: an argument that is not a keyword argument. "
|
|||
|
"Positional arguments can appear at the beginning of an argument list and/or "
|
|||
|
"be passed as elements of an :term:`iterable` preceded by ``*``. For example, "
|
|||
|
"``3`` and ``5`` are both positional arguments in the following calls::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:63
|
|||
|
msgid ""
|
|||
|
"Arguments are assigned to the named local variables in a function body. See "
|
|||
|
"the :ref:`calls` section for the rules governing this assignment. "
|
|||
|
"Syntactically, any expression can be used to represent an argument; the "
|
|||
|
"evaluated value is assigned to the local variable."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:68
|
|||
|
msgid ""
|
|||
|
"See also the :term:`parameter` glossary entry, the FAQ question on :ref:`the "
|
|||
|
"difference between arguments and parameters <faq-argument-vs-parameter>`, "
|
|||
|
"and :pep:`362`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:71
|
|||
|
msgid "asynchronous context manager"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:73
|
|||
|
msgid ""
|
|||
|
"An object which controls the environment seen in an :keyword:`async with` "
|
|||
|
"statement by defining :meth:`__aenter__` and :meth:`__aexit__` methods. "
|
|||
|
"Introduced by :pep:`492`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:76
|
|||
|
msgid "asynchronous iterable"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:78
|
|||
|
msgid ""
|
|||
|
"An object, that can be used in an :keyword:`async for` statement. Must "
|
|||
|
"return an :term:`asynchronous iterator` from its :meth:`__aiter__` method. "
|
|||
|
"Introduced by :pep:`492`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:81
|
|||
|
msgid "asynchronous iterator"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:83
|
|||
|
msgid ""
|
|||
|
"An object that implements :meth:`__aiter__` and :meth:`__anext__` methods. "
|
|||
|
"``__anext__`` must return an :term:`awaitable` object. :keyword:`async for` "
|
|||
|
"resolves awaitable returned from asynchronous iterator's :meth:`__anext__` "
|
|||
|
"method until it raises :exc:`StopAsyncIteration` exception. Introduced by :"
|
|||
|
"pep:`492`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:88
|
|||
|
msgid "attribute"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:90
|
|||
|
msgid ""
|
|||
|
"A value associated with an object which is referenced by name using dotted "
|
|||
|
"expressions. For example, if an object *o* has an attribute *a* it would be "
|
|||
|
"referenced as *o.a*."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:93
|
|||
|
msgid "awaitable"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:95
|
|||
|
msgid ""
|
|||
|
"An object that can be used in an :keyword:`await` expression. Can be a :"
|
|||
|
"term:`coroutine` or an object with an :meth:`__await__` method. See also :"
|
|||
|
"pep:`492`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:98
|
|||
|
msgid "BDFL"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:100
|
|||
|
msgid ""
|
|||
|
"Benevolent Dictator For Life, a.k.a. `Guido van Rossum <https://www.python."
|
|||
|
"org/~guido/>`_, Python's creator."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:102
|
|||
|
msgid "binary file"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:104
|
|||
|
msgid ""
|
|||
|
"A :term:`file object` able to read and write :term:`bytes-like objects "
|
|||
|
"<bytes-like object>`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:108
|
|||
|
msgid "A :term:`text file` reads and writes :class:`str` objects."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:109
|
|||
|
msgid "bytes-like object"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:111
|
|||
|
msgid ""
|
|||
|
"An object that supports the :ref:`bufferobjects` and can export a C-:term:"
|
|||
|
"`contiguous` buffer. This includes all :class:`bytes`, :class:`bytearray`, "
|
|||
|
"and :class:`array.array` objects, as well as many common :class:`memoryview` "
|
|||
|
"objects. Bytes-like objects can be used for various operations that work "
|
|||
|
"with binary data; these include compression, saving to a binary file, and "
|
|||
|
"sending over a socket."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:118
|
|||
|
msgid ""
|
|||
|
"Some operations need the binary data to be mutable. The documentation often "
|
|||
|
"refers to these as \"read-write bytes-like objects\". Example mutable "
|
|||
|
"buffer objects include :class:`bytearray` and a :class:`memoryview` of a :"
|
|||
|
"class:`bytearray`. Other operations require the binary data to be stored in "
|
|||
|
"immutable objects (\"read-only bytes-like objects\"); examples of these "
|
|||
|
"include :class:`bytes` and a :class:`memoryview` of a :class:`bytes` object."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:126
|
|||
|
msgid "bytecode"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:128
|
|||
|
msgid ""
|
|||
|
"Python source code is compiled into bytecode, the internal representation of "
|
|||
|
"a Python program in the CPython interpreter. The bytecode is also cached in "
|
|||
|
"``.pyc`` and ``.pyo`` files so that executing the same file is faster the "
|
|||
|
"second time (recompilation from source to bytecode can be avoided). This "
|
|||
|
"\"intermediate language\" is said to run on a :term:`virtual machine` that "
|
|||
|
"executes the machine code corresponding to each bytecode. Do note that "
|
|||
|
"bytecodes are not expected to work between different Python virtual "
|
|||
|
"machines, nor to be stable between Python releases."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:138
|
|||
|
msgid ""
|
|||
|
"A list of bytecode instructions can be found in the documentation for :ref:"
|
|||
|
"`the dis module <bytecodes>`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:140
|
|||
|
msgid "class"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:142
|
|||
|
msgid ""
|
|||
|
"A template for creating user-defined objects. Class definitions normally "
|
|||
|
"contain method definitions which operate on instances of the class."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:145
|
|||
|
msgid "coercion"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:147
|
|||
|
msgid ""
|
|||
|
"The implicit conversion of an instance of one type to another during an "
|
|||
|
"operation which involves two arguments of the same type. For example, "
|
|||
|
"``int(3.15)`` converts the floating point number to the integer ``3``, but "
|
|||
|
"in ``3+4.5``, each argument is of a different type (one int, one float), and "
|
|||
|
"both must be converted to the same type before they can be added or it will "
|
|||
|
"raise a ``TypeError``. Without coercion, all arguments of even compatible "
|
|||
|
"types would have to be normalized to the same value by the programmer, e.g., "
|
|||
|
"``float(3)+4.5`` rather than just ``3+4.5``."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:155
|
|||
|
msgid "complex number"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:157
|
|||
|
msgid ""
|
|||
|
"An extension of the familiar real number system in which all numbers are "
|
|||
|
"expressed as a sum of a real part and an imaginary part. Imaginary numbers "
|
|||
|
"are real multiples of the imaginary unit (the square root of ``-1``), often "
|
|||
|
"written ``i`` in mathematics or ``j`` in engineering. Python has built-in "
|
|||
|
"support for complex numbers, which are written with this latter notation; "
|
|||
|
"the imaginary part is written with a ``j`` suffix, e.g., ``3+1j``. To get "
|
|||
|
"access to complex equivalents of the :mod:`math` module, use :mod:`cmath`. "
|
|||
|
"Use of complex numbers is a fairly advanced mathematical feature. If you're "
|
|||
|
"not aware of a need for them, it's almost certain you can safely ignore them."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:167
|
|||
|
msgid "context manager"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:169
|
|||
|
msgid ""
|
|||
|
"An object which controls the environment seen in a :keyword:`with` statement "
|
|||
|
"by defining :meth:`__enter__` and :meth:`__exit__` methods. See :pep:`343`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:172
|
|||
|
msgid "contiguous"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:176
|
|||
|
msgid ""
|
|||
|
"A buffer is considered contiguous exactly if it is either *C-contiguous* or "
|
|||
|
"*Fortran contiguous*. Zero-dimensional buffers are C and Fortran "
|
|||
|
"contiguous. In one-dimensional arrays, the items must be laid out in memory "
|
|||
|
"next to each other, in order of increasing indexes starting from zero. In "
|
|||
|
"multidimensional C-contiguous arrays, the last index varies the fastest when "
|
|||
|
"visiting items in order of memory address. However, in Fortran contiguous "
|
|||
|
"arrays, the first index varies the fastest."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:184
|
|||
|
msgid "coroutine"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:186
|
|||
|
msgid ""
|
|||
|
"Coroutines is a more generalized form of subroutines. Subroutines are "
|
|||
|
"entered at one point and exited at another point. Coroutines can be "
|
|||
|
"entered, exited, and resumed at many different points. They can be "
|
|||
|
"implemented with the :keyword:`async def` statement. See also :pep:`492`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:191
|
|||
|
msgid "coroutine function"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:193
|
|||
|
msgid ""
|
|||
|
"A function which returns a :term:`coroutine` object. A coroutine function "
|
|||
|
"may be defined with the :keyword:`async def` statement, and may contain :"
|
|||
|
"keyword:`await`, :keyword:`async for`, and :keyword:`async with` keywords. "
|
|||
|
"These were introduced by :pep:`492`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:198
|
|||
|
msgid "CPython"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:200
|
|||
|
msgid ""
|
|||
|
"The canonical implementation of the Python programming language, as "
|
|||
|
"distributed on `python.org <https://www.python.org>`_. The term \"CPython\" "
|
|||
|
"is used when necessary to distinguish this implementation from others such "
|
|||
|
"as Jython or IronPython."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:204
|
|||
|
msgid "decorator"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:206
|
|||
|
msgid ""
|
|||
|
"A function returning another function, usually applied as a function "
|
|||
|
"transformation using the ``@wrapper`` syntax. Common examples for "
|
|||
|
"decorators are :func:`classmethod` and :func:`staticmethod`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:210
|
|||
|
msgid ""
|
|||
|
"The decorator syntax is merely syntactic sugar, the following two function "
|
|||
|
"definitions are semantically equivalent::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:221
|
|||
|
msgid ""
|
|||
|
"The same concept exists for classes, but is less commonly used there. See "
|
|||
|
"the documentation for :ref:`function definitions <function>` and :ref:`class "
|
|||
|
"definitions <class>` for more about decorators."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:224
|
|||
|
msgid "descriptor"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:226
|
|||
|
msgid ""
|
|||
|
"Any object which defines the methods :meth:`__get__`, :meth:`__set__`, or :"
|
|||
|
"meth:`__delete__`. When a class attribute is a descriptor, its special "
|
|||
|
"binding behavior is triggered upon attribute lookup. Normally, using *a.b* "
|
|||
|
"to get, set or delete an attribute looks up the object named *b* in the "
|
|||
|
"class dictionary for *a*, but if *b* is a descriptor, the respective "
|
|||
|
"descriptor method gets called. Understanding descriptors is a key to a deep "
|
|||
|
"understanding of Python because they are the basis for many features "
|
|||
|
"including functions, methods, properties, class methods, static methods, and "
|
|||
|
"reference to super classes."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:236
|
|||
|
msgid ""
|
|||
|
"For more information about descriptors' methods, see :ref:`descriptors`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:237
|
|||
|
msgid "dictionary"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:239
|
|||
|
msgid ""
|
|||
|
"An associative array, where arbitrary keys are mapped to values. The keys "
|
|||
|
"can be any object with :meth:`__hash__` and :meth:`__eq__` methods. Called a "
|
|||
|
"hash in Perl."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:242
|
|||
|
msgid "dictionary view"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:244
|
|||
|
msgid ""
|
|||
|
"The objects returned from :meth:`dict.keys`, :meth:`dict.values`, and :meth:"
|
|||
|
"`dict.items` are called dictionary views. They provide a dynamic view on the "
|
|||
|
"dictionary’s entries, which means that when the dictionary changes, the view "
|
|||
|
"reflects these changes. To force the dictionary view to become a full list "
|
|||
|
"use ``list(dictview)``. See :ref:`dict-views`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:250
|
|||
|
msgid "docstring"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:252
|
|||
|
msgid ""
|
|||
|
"A string literal which appears as the first expression in a class, function "
|
|||
|
"or module. While ignored when the suite is executed, it is recognized by "
|
|||
|
"the compiler and put into the :attr:`__doc__` attribute of the enclosing "
|
|||
|
"class, function or module. Since it is available via introspection, it is "
|
|||
|
"the canonical place for documentation of the object."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:258
|
|||
|
msgid "duck-typing"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:260
|
|||
|
msgid ""
|
|||
|
"A programming style which does not look at an object's type to determine if "
|
|||
|
"it has the right interface; instead, the method or attribute is simply "
|
|||
|
"called or used (\"If it looks like a duck and quacks like a duck, it must be "
|
|||
|
"a duck.\") By emphasizing interfaces rather than specific types, well-"
|
|||
|
"designed code improves its flexibility by allowing polymorphic "
|
|||
|
"substitution. Duck-typing avoids tests using :func:`type` or :func:"
|
|||
|
"`isinstance`. (Note, however, that duck-typing can be complemented with :"
|
|||
|
"term:`abstract base classes <abstract base class>`.) Instead, it typically "
|
|||
|
"employs :func:`hasattr` tests or :term:`EAFP` programming."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:269
|
|||
|
msgid "EAFP"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:271
|
|||
|
msgid ""
|
|||
|
"Easier to ask for forgiveness than permission. This common Python coding "
|
|||
|
"style assumes the existence of valid keys or attributes and catches "
|
|||
|
"exceptions if the assumption proves false. This clean and fast style is "
|
|||
|
"characterized by the presence of many :keyword:`try` and :keyword:`except` "
|
|||
|
"statements. The technique contrasts with the :term:`LBYL` style common to "
|
|||
|
"many other languages such as C."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:277
|
|||
|
msgid "expression"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:279
|
|||
|
msgid ""
|
|||
|
"A piece of syntax which can be evaluated to some value. In other words, an "
|
|||
|
"expression is an accumulation of expression elements like literals, names, "
|
|||
|
"attribute access, operators or function calls which all return a value. In "
|
|||
|
"contrast to many other languages, not all language constructs are "
|
|||
|
"expressions. There are also :term:`statement`\\s which cannot be used as "
|
|||
|
"expressions, such as :keyword:`if`. Assignments are also statements, not "
|
|||
|
"expressions."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:286
|
|||
|
msgid "extension module"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:288
|
|||
|
msgid ""
|
|||
|
"A module written in C or C++, using Python's C API to interact with the core "
|
|||
|
"and with user code."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:290
|
|||
|
msgid "file object"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:292
|
|||
|
msgid ""
|
|||
|
"An object exposing a file-oriented API (with methods such as :meth:`read()` "
|
|||
|
"or :meth:`write()`) to an underlying resource. Depending on the way it was "
|
|||
|
"created, a file object can mediate access to a real on-disk file or to "
|
|||
|
"another type of storage or communication device (for example standard input/"
|
|||
|
"output, in-memory buffers, sockets, pipes, etc.). File objects are also "
|
|||
|
"called :dfn:`file-like objects` or :dfn:`streams`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:300
|
|||
|
msgid ""
|
|||
|
"There are actually three categories of file objects: raw :term:`binary files "
|
|||
|
"<binary file>`, buffered :term:`binary files <binary file>` and :term:`text "
|
|||
|
"files <text file>`. Their interfaces are defined in the :mod:`io` module. "
|
|||
|
"The canonical way to create a file object is by using the :func:`open` "
|
|||
|
"function."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:305
|
|||
|
msgid "file-like object"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:307
|
|||
|
msgid "A synonym for :term:`file object`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:308
|
|||
|
msgid "finder"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:310
|
|||
|
msgid ""
|
|||
|
"An object that tries to find the :term:`loader` for a module that is being "
|
|||
|
"imported."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:313
|
|||
|
msgid ""
|
|||
|
"Since Python 3.3, there are two types of finder: :term:`meta path finders "
|
|||
|
"<meta path finder>` for use with :data:`sys.meta_path`, and :term:`path "
|
|||
|
"entry finders <path entry finder>` for use with :data:`sys.path_hooks`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:317
|
|||
|
msgid "See :pep:`302`, :pep:`420` and :pep:`451` for much more detail."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:318
|
|||
|
msgid "floor division"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:320
|
|||
|
msgid ""
|
|||
|
"Mathematical division that rounds down to nearest integer. The floor "
|
|||
|
"division operator is ``//``. For example, the expression ``11 // 4`` "
|
|||
|
"evaluates to ``2`` in contrast to the ``2.75`` returned by float true "
|
|||
|
"division. Note that ``(-11) // 4`` is ``-3`` because that is ``-2.75`` "
|
|||
|
"rounded *downward*. See :pep:`238`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:325
|
|||
|
msgid "function"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:327
|
|||
|
msgid ""
|
|||
|
"A series of statements which returns some value to a caller. It can also be "
|
|||
|
"passed zero or more :term:`arguments <argument>` which may be used in the "
|
|||
|
"execution of the body. See also :term:`parameter`, :term:`method`, and the :"
|
|||
|
"ref:`function` section."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:331
|
|||
|
msgid "function annotation"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:333
|
|||
|
msgid ""
|
|||
|
"An arbitrary metadata value associated with a function parameter or return "
|
|||
|
"value. Its syntax is explained in section :ref:`function`. Annotations may "
|
|||
|
"be accessed via the :attr:`__annotations__` special attribute of a function "
|
|||
|
"object."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:338
|
|||
|
msgid ""
|
|||
|
"Python itself does not assign any particular meaning to function "
|
|||
|
"annotations. They are intended to be interpreted by third-party libraries or "
|
|||
|
"tools. See :pep:`3107`, which describes some of their potential uses."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:341
|
|||
|
msgid "__future__"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:343
|
|||
|
msgid ""
|
|||
|
"A pseudo-module which programmers can use to enable new language features "
|
|||
|
"which are not compatible with the current interpreter."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:346
|
|||
|
msgid ""
|
|||
|
"By importing the :mod:`__future__` module and evaluating its variables, you "
|
|||
|
"can see when a new feature was first added to the language and when it "
|
|||
|
"becomes the default::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:353
|
|||
|
msgid "garbage collection"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:355
|
|||
|
msgid ""
|
|||
|
"The process of freeing memory when it is not used anymore. Python performs "
|
|||
|
"garbage collection via reference counting and a cyclic garbage collector "
|
|||
|
"that is able to detect and break reference cycles."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:360
|
|||
|
msgid "generator"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:362
|
|||
|
msgid ""
|
|||
|
"A function which returns a :term:`generator iterator`. It looks like a "
|
|||
|
"normal function except that it contains :keyword:`yield` expressions for "
|
|||
|
"producing a series of values usable in a for-loop or that can be retrieved "
|
|||
|
"one at a time with the :func:`next` function."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:367
|
|||
|
msgid ""
|
|||
|
"Usually refers to a generator function, but may refer to a *generator "
|
|||
|
"iterator* in some contexts. In cases where the intended meaning isn't "
|
|||
|
"clear, using the full terms avoids ambiguity."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:370
|
|||
|
msgid "generator iterator"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:372
|
|||
|
msgid "An object created by a :term:`generator` function."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:374
|
|||
|
msgid ""
|
|||
|
"Each :keyword:`yield` temporarily suspends processing, remembering the "
|
|||
|
"location execution state (including local variables and pending try-"
|
|||
|
"statements). When the *generator iterator* resumes, it picks-up where it "
|
|||
|
"left-off (in contrast to functions which start fresh on every invocation)."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:381
|
|||
|
msgid "generator expression"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:383
|
|||
|
msgid ""
|
|||
|
"An expression that returns an iterator. It looks like a normal expression "
|
|||
|
"followed by a :keyword:`for` expression defining a loop variable, range, and "
|
|||
|
"an optional :keyword:`if` expression. The combined expression generates "
|
|||
|
"values for an enclosing function::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:390
|
|||
|
msgid "generic function"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:392
|
|||
|
msgid ""
|
|||
|
"A function composed of multiple functions implementing the same operation "
|
|||
|
"for different types. Which implementation should be used during a call is "
|
|||
|
"determined by the dispatch algorithm."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:396
|
|||
|
msgid ""
|
|||
|
"See also the :term:`single dispatch` glossary entry, the :func:`functools."
|
|||
|
"singledispatch` decorator, and :pep:`443`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:399
|
|||
|
msgid "GIL"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:401
|
|||
|
msgid "See :term:`global interpreter lock`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:402
|
|||
|
msgid "global interpreter lock"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:404
|
|||
|
msgid ""
|
|||
|
"The mechanism used by the :term:`CPython` interpreter to assure that only "
|
|||
|
"one thread executes Python :term:`bytecode` at a time. This simplifies the "
|
|||
|
"CPython implementation by making the object model (including critical built-"
|
|||
|
"in types such as :class:`dict`) implicitly safe against concurrent access. "
|
|||
|
"Locking the entire interpreter makes it easier for the interpreter to be "
|
|||
|
"multi-threaded, at the expense of much of the parallelism afforded by multi-"
|
|||
|
"processor machines."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:413
|
|||
|
msgid ""
|
|||
|
"However, some extension modules, either standard or third-party, are "
|
|||
|
"designed so as to release the GIL when doing computationally-intensive tasks "
|
|||
|
"such as compression or hashing. Also, the GIL is always released when doing "
|
|||
|
"I/O."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:418
|
|||
|
msgid ""
|
|||
|
"Past efforts to create a \"free-threaded\" interpreter (one which locks "
|
|||
|
"shared data at a much finer granularity) have not been successful because "
|
|||
|
"performance suffered in the common single-processor case. It is believed "
|
|||
|
"that overcoming this performance issue would make the implementation much "
|
|||
|
"more complicated and therefore costlier to maintain."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:423
|
|||
|
msgid "hashable"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:425
|
|||
|
msgid ""
|
|||
|
"An object is *hashable* if it has a hash value which never changes during "
|
|||
|
"its lifetime (it needs a :meth:`__hash__` method), and can be compared to "
|
|||
|
"other objects (it needs an :meth:`__eq__` method). Hashable objects which "
|
|||
|
"compare equal must have the same hash value."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:430
|
|||
|
msgid ""
|
|||
|
"Hashability makes an object usable as a dictionary key and a set member, "
|
|||
|
"because these data structures use the hash value internally."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:433
|
|||
|
msgid ""
|
|||
|
"All of Python's immutable built-in objects are hashable, while no mutable "
|
|||
|
"containers (such as lists or dictionaries) are. Objects which are instances "
|
|||
|
"of user-defined classes are hashable by default; they all compare unequal "
|
|||
|
"(except with themselves), and their hash value is derived from their :func:"
|
|||
|
"`id`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:438
|
|||
|
msgid "IDLE"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:440
|
|||
|
msgid ""
|
|||
|
"An Integrated Development Environment for Python. IDLE is a basic editor "
|
|||
|
"and interpreter environment which ships with the standard distribution of "
|
|||
|
"Python."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:443
|
|||
|
msgid "immutable"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:445
|
|||
|
msgid ""
|
|||
|
"An object with a fixed value. Immutable objects include numbers, strings "
|
|||
|
"and tuples. Such an object cannot be altered. A new object has to be "
|
|||
|
"created if a different value has to be stored. They play an important role "
|
|||
|
"in places where a constant hash value is needed, for example as a key in a "
|
|||
|
"dictionary."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:450
|
|||
|
msgid "import path"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:452
|
|||
|
msgid ""
|
|||
|
"A list of locations (or :term:`path entries <path entry>`) that are searched "
|
|||
|
"by the :term:`path based finder` for modules to import. During import, this "
|
|||
|
"list of locations usually comes from :data:`sys.path`, but for subpackages "
|
|||
|
"it may also come from the parent package's ``__path__`` attribute."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:457
|
|||
|
msgid "importing"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:459
|
|||
|
msgid ""
|
|||
|
"The process by which Python code in one module is made available to Python "
|
|||
|
"code in another module."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:461
|
|||
|
msgid "importer"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:463
|
|||
|
msgid ""
|
|||
|
"An object that both finds and loads a module; both a :term:`finder` and :"
|
|||
|
"term:`loader` object."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:465
|
|||
|
msgid "interactive"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:467
|
|||
|
msgid ""
|
|||
|
"Python has an interactive interpreter which means you can enter statements "
|
|||
|
"and expressions at the interpreter prompt, immediately execute them and see "
|
|||
|
"their results. Just launch ``python`` with no arguments (possibly by "
|
|||
|
"selecting it from your computer's main menu). It is a very powerful way to "
|
|||
|
"test out new ideas or inspect modules and packages (remember ``help(x)``)."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:473
|
|||
|
msgid "interpreted"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:475
|
|||
|
msgid ""
|
|||
|
"Python is an interpreted language, as opposed to a compiled one, though the "
|
|||
|
"distinction can be blurry because of the presence of the bytecode compiler. "
|
|||
|
"This means that source files can be run directly without explicitly creating "
|
|||
|
"an executable which is then run. Interpreted languages typically have a "
|
|||
|
"shorter development/debug cycle than compiled ones, though their programs "
|
|||
|
"generally also run more slowly. See also :term:`interactive`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:482
|
|||
|
msgid "interpreter shutdown"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:484
|
|||
|
msgid ""
|
|||
|
"When asked to shut down, the Python interpreter enters a special phase where "
|
|||
|
"it gradually releases all allocated resources, such as modules and various "
|
|||
|
"critical internal structures. It also makes several calls to the :term:"
|
|||
|
"`garbage collector <garbage collection>`. This can trigger the execution of "
|
|||
|
"code in user-defined destructors or weakref callbacks. Code executed during "
|
|||
|
"the shutdown phase can encounter various exceptions as the resources it "
|
|||
|
"relies on may not function anymore (common examples are library modules or "
|
|||
|
"the warnings machinery)."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:493
|
|||
|
msgid ""
|
|||
|
"The main reason for interpreter shutdown is that the ``__main__`` module or "
|
|||
|
"the script being run has finished executing."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:495
|
|||
|
msgid "iterable"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:497
|
|||
|
msgid ""
|
|||
|
"An object capable of returning its members one at a time. Examples of "
|
|||
|
"iterables include all sequence types (such as :class:`list`, :class:`str`, "
|
|||
|
"and :class:`tuple`) and some non-sequence types like :class:`dict`, :term:"
|
|||
|
"`file objects <file object>`, and objects of any classes you define with an :"
|
|||
|
"meth:`__iter__` or :meth:`__getitem__` method. Iterables can be used in a :"
|
|||
|
"keyword:`for` loop and in many other places where a sequence is needed (:"
|
|||
|
"func:`zip`, :func:`map`, ...). When an iterable object is passed as an "
|
|||
|
"argument to the built-in function :func:`iter`, it returns an iterator for "
|
|||
|
"the object. This iterator is good for one pass over the set of values. "
|
|||
|
"When using iterables, it is usually not necessary to call :func:`iter` or "
|
|||
|
"deal with iterator objects yourself. The ``for`` statement does that "
|
|||
|
"automatically for you, creating a temporary unnamed variable to hold the "
|
|||
|
"iterator for the duration of the loop. See also :term:`iterator`, :term:"
|
|||
|
"`sequence`, and :term:`generator`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:511
|
|||
|
msgid "iterator"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:513
|
|||
|
msgid ""
|
|||
|
"An object representing a stream of data. Repeated calls to the iterator's :"
|
|||
|
"meth:`~iterator.__next__` method (or passing it to the built-in function :"
|
|||
|
"func:`next`) return successive items in the stream. When no more data are "
|
|||
|
"available a :exc:`StopIteration` exception is raised instead. At this "
|
|||
|
"point, the iterator object is exhausted and any further calls to its :meth:"
|
|||
|
"`__next__` method just raise :exc:`StopIteration` again. Iterators are "
|
|||
|
"required to have an :meth:`__iter__` method that returns the iterator object "
|
|||
|
"itself so every iterator is also iterable and may be used in most places "
|
|||
|
"where other iterables are accepted. One notable exception is code which "
|
|||
|
"attempts multiple iteration passes. A container object (such as a :class:"
|
|||
|
"`list`) produces a fresh new iterator each time you pass it to the :func:"
|
|||
|
"`iter` function or use it in a :keyword:`for` loop. Attempting this with an "
|
|||
|
"iterator will just return the same exhausted iterator object used in the "
|
|||
|
"previous iteration pass, making it appear like an empty container."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:528
|
|||
|
msgid "More information can be found in :ref:`typeiter`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:529
|
|||
|
msgid "key function"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:531
|
|||
|
msgid ""
|
|||
|
"A key function or collation function is a callable that returns a value used "
|
|||
|
"for sorting or ordering. For example, :func:`locale.strxfrm` is used to "
|
|||
|
"produce a sort key that is aware of locale specific sort conventions."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:536
|
|||
|
msgid ""
|
|||
|
"A number of tools in Python accept key functions to control how elements are "
|
|||
|
"ordered or grouped. They include :func:`min`, :func:`max`, :func:`sorted`, :"
|
|||
|
"meth:`list.sort`, :func:`heapq.merge`, :func:`heapq.nsmallest`, :func:`heapq."
|
|||
|
"nlargest`, and :func:`itertools.groupby`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:542
|
|||
|
msgid ""
|
|||
|
"There are several ways to create a key function. For example. the :meth:"
|
|||
|
"`str.lower` method can serve as a key function for case insensitive sorts. "
|
|||
|
"Alternatively, a key function can be built from a :keyword:`lambda` "
|
|||
|
"expression such as ``lambda r: (r[0], r[2])``. Also, the :mod:`operator` "
|
|||
|
"module provides three key function constructors: :func:`~operator."
|
|||
|
"attrgetter`, :func:`~operator.itemgetter`, and :func:`~operator."
|
|||
|
"methodcaller`. See the :ref:`Sorting HOW TO <sortinghowto>` for examples of "
|
|||
|
"how to create and use key functions."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:550
|
|||
|
msgid "keyword argument"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:552 ../Doc/glossary.rst:796
|
|||
|
msgid "See :term:`argument`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:553
|
|||
|
msgid "lambda"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:555
|
|||
|
msgid ""
|
|||
|
"An anonymous inline function consisting of a single :term:`expression` which "
|
|||
|
"is evaluated when the function is called. The syntax to create a lambda "
|
|||
|
"function is ``lambda [arguments]: expression``"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:558
|
|||
|
msgid "LBYL"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:560
|
|||
|
msgid ""
|
|||
|
"Look before you leap. This coding style explicitly tests for pre-conditions "
|
|||
|
"before making calls or lookups. This style contrasts with the :term:`EAFP` "
|
|||
|
"approach and is characterized by the presence of many :keyword:`if` "
|
|||
|
"statements."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:565
|
|||
|
msgid ""
|
|||
|
"In a multi-threaded environment, the LBYL approach can risk introducing a "
|
|||
|
"race condition between \"the looking\" and \"the leaping\". For example, "
|
|||
|
"the code, ``if key in mapping: return mapping[key]`` can fail if another "
|
|||
|
"thread removes *key* from *mapping* after the test, but before the lookup. "
|
|||
|
"This issue can be solved with locks or by using the EAFP approach."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:570
|
|||
|
msgid "list"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:572
|
|||
|
msgid ""
|
|||
|
"A built-in Python :term:`sequence`. Despite its name it is more akin to an "
|
|||
|
"array in other languages than to a linked list since access to elements are "
|
|||
|
"O(1)."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:575
|
|||
|
msgid "list comprehension"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:577
|
|||
|
msgid ""
|
|||
|
"A compact way to process all or part of the elements in a sequence and "
|
|||
|
"return a list with the results. ``result = ['{:#04x}'.format(x) for x in "
|
|||
|
"range(256) if x % 2 == 0]`` generates a list of strings containing even hex "
|
|||
|
"numbers (0x..) in the range from 0 to 255. The :keyword:`if` clause is "
|
|||
|
"optional. If omitted, all elements in ``range(256)`` are processed."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:583
|
|||
|
msgid "loader"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:585
|
|||
|
msgid ""
|
|||
|
"An object that loads a module. It must define a method named :meth:"
|
|||
|
"`load_module`. A loader is typically returned by a :term:`finder`. See :pep:"
|
|||
|
"`302` for details and :class:`importlib.abc.Loader` for an :term:`abstract "
|
|||
|
"base class`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:589
|
|||
|
msgid "mapping"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:591
|
|||
|
msgid ""
|
|||
|
"A container object that supports arbitrary key lookups and implements the "
|
|||
|
"methods specified in the :class:`~collections.abc.Mapping` or :class:"
|
|||
|
"`~collections.abc.MutableMapping` :ref:`abstract base classes <collections-"
|
|||
|
"abstract-base-classes>`. Examples include :class:`dict`, :class:"
|
|||
|
"`collections.defaultdict`, :class:`collections.OrderedDict` and :class:"
|
|||
|
"`collections.Counter`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:597
|
|||
|
msgid "meta path finder"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:599
|
|||
|
msgid ""
|
|||
|
"A :term:`finder` returned by a search of :data:`sys.meta_path`. Meta path "
|
|||
|
"finders are related to, but different from :term:`path entry finders <path "
|
|||
|
"entry finder>`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:603
|
|||
|
msgid ""
|
|||
|
"See :class:`importlib.abc.MetaPathFinder` for the methods that meta path "
|
|||
|
"finders implement."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:605
|
|||
|
msgid "metaclass"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:607
|
|||
|
msgid ""
|
|||
|
"The class of a class. Class definitions create a class name, a class "
|
|||
|
"dictionary, and a list of base classes. The metaclass is responsible for "
|
|||
|
"taking those three arguments and creating the class. Most object oriented "
|
|||
|
"programming languages provide a default implementation. What makes Python "
|
|||
|
"special is that it is possible to create custom metaclasses. Most users "
|
|||
|
"never need this tool, but when the need arises, metaclasses can provide "
|
|||
|
"powerful, elegant solutions. They have been used for logging attribute "
|
|||
|
"access, adding thread-safety, tracking object creation, implementing "
|
|||
|
"singletons, and many other tasks."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:617
|
|||
|
msgid "More information can be found in :ref:`metaclasses`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:618
|
|||
|
msgid "method"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:620
|
|||
|
msgid ""
|
|||
|
"A function which is defined inside a class body. If called as an attribute "
|
|||
|
"of an instance of that class, the method will get the instance object as its "
|
|||
|
"first :term:`argument` (which is usually called ``self``). See :term:"
|
|||
|
"`function` and :term:`nested scope`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:624
|
|||
|
msgid "method resolution order"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:626
|
|||
|
msgid ""
|
|||
|
"Method Resolution Order is the order in which base classes are searched for "
|
|||
|
"a member during lookup. See `The Python 2.3 Method Resolution Order <https://"
|
|||
|
"www.python.org/download/releases/2.3/mro/>`_ for details of the algorithm "
|
|||
|
"used by the Python interpreter since the 2.3 release."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:630
|
|||
|
msgid "module"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:632
|
|||
|
msgid ""
|
|||
|
"An object that serves as an organizational unit of Python code. Modules "
|
|||
|
"have a namespace containing arbitrary Python objects. Modules are loaded "
|
|||
|
"into Python by the process of :term:`importing`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:636
|
|||
|
msgid "See also :term:`package`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:637
|
|||
|
msgid "module spec"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:639
|
|||
|
msgid ""
|
|||
|
"A namespace containing the import-related information used to load a module. "
|
|||
|
"An instance of :class:`importlib.machinery.ModuleSpec`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:641
|
|||
|
msgid "MRO"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:643
|
|||
|
msgid "See :term:`method resolution order`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:644
|
|||
|
msgid "mutable"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:646
|
|||
|
msgid ""
|
|||
|
"Mutable objects can change their value but keep their :func:`id`. See also :"
|
|||
|
"term:`immutable`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:648
|
|||
|
msgid "named tuple"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:650
|
|||
|
msgid ""
|
|||
|
"Any tuple-like class whose indexable elements are also accessible using "
|
|||
|
"named attributes (for example, :func:`time.localtime` returns a tuple-like "
|
|||
|
"object where the *year* is accessible either with an index such as ``t[0]`` "
|
|||
|
"or with a named attribute like ``t.tm_year``)."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:655
|
|||
|
msgid ""
|
|||
|
"A named tuple can be a built-in type such as :class:`time.struct_time`, or "
|
|||
|
"it can be created with a regular class definition. A full featured named "
|
|||
|
"tuple can also be created with the factory function :func:`collections."
|
|||
|
"namedtuple`. The latter approach automatically provides extra features such "
|
|||
|
"as a self-documenting representation like ``Employee(name='jones', "
|
|||
|
"title='programmer')``."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:661
|
|||
|
msgid "namespace"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:663
|
|||
|
msgid ""
|
|||
|
"The place where a variable is stored. Namespaces are implemented as "
|
|||
|
"dictionaries. There are the local, global and built-in namespaces as well "
|
|||
|
"as nested namespaces in objects (in methods). Namespaces support modularity "
|
|||
|
"by preventing naming conflicts. For instance, the functions :func:`builtins."
|
|||
|
"open <.open>` and :func:`os.open` are distinguished by their namespaces. "
|
|||
|
"Namespaces also aid readability and maintainability by making it clear which "
|
|||
|
"module implements a function. For instance, writing :func:`random.seed` or :"
|
|||
|
"func:`itertools.islice` makes it clear that those functions are implemented "
|
|||
|
"by the :mod:`random` and :mod:`itertools` modules, respectively."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:673
|
|||
|
msgid "namespace package"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:675
|
|||
|
msgid ""
|
|||
|
"A :pep:`420` :term:`package` which serves only as a container for "
|
|||
|
"subpackages. Namespace packages may have no physical representation, and "
|
|||
|
"specifically are not like a :term:`regular package` because they have no "
|
|||
|
"``__init__.py`` file."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:680
|
|||
|
msgid "See also :term:`module`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:681
|
|||
|
msgid "nested scope"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:683
|
|||
|
msgid ""
|
|||
|
"The ability to refer to a variable in an enclosing definition. For "
|
|||
|
"instance, a function defined inside another function can refer to variables "
|
|||
|
"in the outer function. Note that nested scopes by default work only for "
|
|||
|
"reference and not for assignment. Local variables both read and write in "
|
|||
|
"the innermost scope. Likewise, global variables read and write to the "
|
|||
|
"global namespace. The :keyword:`nonlocal` allows writing to outer scopes."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:690
|
|||
|
msgid "new-style class"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:692
|
|||
|
msgid ""
|
|||
|
"Old name for the flavor of classes now used for all class objects. In "
|
|||
|
"earlier Python versions, only new-style classes could use Python's newer, "
|
|||
|
"versatile features like :attr:`~object.__slots__`, descriptors, properties, :"
|
|||
|
"meth:`__getattribute__`, class methods, and static methods."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:696
|
|||
|
msgid "object"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:698
|
|||
|
msgid ""
|
|||
|
"Any data with state (attributes or value) and defined behavior (methods). "
|
|||
|
"Also the ultimate base class of any :term:`new-style class`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:701
|
|||
|
msgid "package"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:703
|
|||
|
msgid ""
|
|||
|
"A Python :term:`module` which can contain submodules or recursively, "
|
|||
|
"subpackages. Technically, a package is a Python module with an ``__path__`` "
|
|||
|
"attribute."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:707
|
|||
|
msgid "See also :term:`regular package` and :term:`namespace package`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:708
|
|||
|
msgid "parameter"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:710
|
|||
|
msgid ""
|
|||
|
"A named entity in a :term:`function` (or method) definition that specifies "
|
|||
|
"an :term:`argument` (or in some cases, arguments) that the function can "
|
|||
|
"accept. There are five kinds of parameter:"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:714
|
|||
|
msgid ""
|
|||
|
":dfn:`positional-or-keyword`: specifies an argument that can be passed "
|
|||
|
"either :term:`positionally <argument>` or as a :term:`keyword argument "
|
|||
|
"<argument>`. This is the default kind of parameter, for example *foo* and "
|
|||
|
"*bar* in the following::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:723
|
|||
|
msgid ""
|
|||
|
":dfn:`positional-only`: specifies an argument that can be supplied only by "
|
|||
|
"position. Python has no syntax for defining positional-only parameters. "
|
|||
|
"However, some built-in functions have positional-only parameters (e.g. :func:"
|
|||
|
"`abs`)."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:730
|
|||
|
msgid ""
|
|||
|
":dfn:`keyword-only`: specifies an argument that can be supplied only by "
|
|||
|
"keyword. Keyword-only parameters can be defined by including a single var-"
|
|||
|
"positional parameter or bare ``*`` in the parameter list of the function "
|
|||
|
"definition before them, for example *kw_only1* and *kw_only2* in the "
|
|||
|
"following::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:738
|
|||
|
msgid ""
|
|||
|
":dfn:`var-positional`: specifies that an arbitrary sequence of positional "
|
|||
|
"arguments can be provided (in addition to any positional arguments already "
|
|||
|
"accepted by other parameters). Such a parameter can be defined by "
|
|||
|
"prepending the parameter name with ``*``, for example *args* in the "
|
|||
|
"following::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:746
|
|||
|
msgid ""
|
|||
|
":dfn:`var-keyword`: specifies that arbitrarily many keyword arguments can be "
|
|||
|
"provided (in addition to any keyword arguments already accepted by other "
|
|||
|
"parameters). Such a parameter can be defined by prepending the parameter "
|
|||
|
"name with ``**``, for example *kwargs* in the example above."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:752
|
|||
|
msgid ""
|
|||
|
"Parameters can specify both optional and required arguments, as well as "
|
|||
|
"default values for some optional arguments."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:755
|
|||
|
msgid ""
|
|||
|
"See also the :term:`argument` glossary entry, the FAQ question on :ref:`the "
|
|||
|
"difference between arguments and parameters <faq-argument-vs-parameter>`, "
|
|||
|
"the :class:`inspect.Parameter` class, the :ref:`function` section, and :pep:"
|
|||
|
"`362`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:759
|
|||
|
msgid "path entry"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:761
|
|||
|
msgid ""
|
|||
|
"A single location on the :term:`import path` which the :term:`path based "
|
|||
|
"finder` consults to find modules for importing."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:763
|
|||
|
msgid "path entry finder"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:765
|
|||
|
msgid ""
|
|||
|
"A :term:`finder` returned by a callable on :data:`sys.path_hooks` (i.e. a :"
|
|||
|
"term:`path entry hook`) which knows how to locate modules given a :term:"
|
|||
|
"`path entry`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:769
|
|||
|
msgid ""
|
|||
|
"See :class:`importlib.abc.PathEntryFinder` for the methods that path entry "
|
|||
|
"finders implement."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:771
|
|||
|
msgid "path entry hook"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:773
|
|||
|
msgid ""
|
|||
|
"A callable on the :data:`sys.path_hook` list which returns a :term:`path "
|
|||
|
"entry finder` if it knows how to find modules on a specific :term:`path "
|
|||
|
"entry`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:776
|
|||
|
msgid "path based finder"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:778
|
|||
|
msgid ""
|
|||
|
"One of the default :term:`meta path finders <meta path finder>` which "
|
|||
|
"searches an :term:`import path` for modules."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:780
|
|||
|
msgid "path-like object"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:782
|
|||
|
msgid ""
|
|||
|
"An object representing a file system path. A path-like object is either a :"
|
|||
|
"class:`str` or :class:`bytes` object representing a path, or an object "
|
|||
|
"implementing the :class:`os.PathLike` protocol. An object that supports the :"
|
|||
|
"class:`os.PathLike` protocol can be converted to a :class:`str` or :class:"
|
|||
|
"`bytes` file system path by calling the :func:`os.fspath` function; :func:"
|
|||
|
"`os.fsdecode` and :func:`os.fsencode` can be used to guarantee a :class:"
|
|||
|
"`str` or :class:`bytes` result instead, respectively. Introduced by :pep:"
|
|||
|
"`519`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:790
|
|||
|
msgid "portion"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:792
|
|||
|
msgid ""
|
|||
|
"A set of files in a single directory (possibly stored in a zip file) that "
|
|||
|
"contribute to a namespace package, as defined in :pep:`420`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:794
|
|||
|
msgid "positional argument"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:797
|
|||
|
msgid "provisional API"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:799
|
|||
|
msgid ""
|
|||
|
"A provisional API is one which has been deliberately excluded from the "
|
|||
|
"standard library's backwards compatibility guarantees. While major changes "
|
|||
|
"to such interfaces are not expected, as long as they are marked provisional, "
|
|||
|
"backwards incompatible changes (up to and including removal of the "
|
|||
|
"interface) may occur if deemed necessary by core developers. Such changes "
|
|||
|
"will not be made gratuitously -- they will occur only if serious fundamental "
|
|||
|
"flaws are uncovered that were missed prior to the inclusion of the API."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:808
|
|||
|
msgid ""
|
|||
|
"Even for provisional APIs, backwards incompatible changes are seen as a "
|
|||
|
"\"solution of last resort\" - every attempt will still be made to find a "
|
|||
|
"backwards compatible resolution to any identified problems."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:812
|
|||
|
msgid ""
|
|||
|
"This process allows the standard library to continue to evolve over time, "
|
|||
|
"without locking in problematic design errors for extended periods of time. "
|
|||
|
"See :pep:`411` for more details."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:815
|
|||
|
msgid "provisional package"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:817
|
|||
|
msgid "See :term:`provisional API`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:818
|
|||
|
msgid "Python 3000"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:820
|
|||
|
msgid ""
|
|||
|
"Nickname for the Python 3.x release line (coined long ago when the release "
|
|||
|
"of version 3 was something in the distant future.) This is also abbreviated "
|
|||
|
"\"Py3k\"."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:823
|
|||
|
msgid "Pythonic"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:825
|
|||
|
msgid ""
|
|||
|
"An idea or piece of code which closely follows the most common idioms of the "
|
|||
|
"Python language, rather than implementing code using concepts common to "
|
|||
|
"other languages. For example, a common idiom in Python is to loop over all "
|
|||
|
"elements of an iterable using a :keyword:`for` statement. Many other "
|
|||
|
"languages don't have this type of construct, so people unfamiliar with "
|
|||
|
"Python sometimes use a numerical counter instead::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:835
|
|||
|
msgid "As opposed to the cleaner, Pythonic method::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:839
|
|||
|
msgid "qualified name"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:841
|
|||
|
msgid ""
|
|||
|
"A dotted name showing the \"path\" from a module's global scope to a class, "
|
|||
|
"function or method defined in that module, as defined in :pep:`3155`. For "
|
|||
|
"top-level functions and classes, the qualified name is the same as the "
|
|||
|
"object's name::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:858
|
|||
|
msgid ""
|
|||
|
"When used to refer to modules, the *fully qualified name* means the entire "
|
|||
|
"dotted path to the module, including any parent packages, e.g. ``email.mime."
|
|||
|
"text``::"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:865
|
|||
|
msgid "reference count"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:867
|
|||
|
msgid ""
|
|||
|
"The number of references to an object. When the reference count of an "
|
|||
|
"object drops to zero, it is deallocated. Reference counting is generally "
|
|||
|
"not visible to Python code, but it is a key element of the :term:`CPython` "
|
|||
|
"implementation. The :mod:`sys` module defines a :func:`~sys.getrefcount` "
|
|||
|
"function that programmers can call to return the reference count for a "
|
|||
|
"particular object."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:873
|
|||
|
msgid "regular package"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:875
|
|||
|
msgid ""
|
|||
|
"A traditional :term:`package`, such as a directory containing an ``__init__."
|
|||
|
"py`` file."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:878
|
|||
|
msgid "See also :term:`namespace package`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:879
|
|||
|
msgid "__slots__"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:881
|
|||
|
msgid ""
|
|||
|
"A declaration inside a class that saves memory by pre-declaring space for "
|
|||
|
"instance attributes and eliminating instance dictionaries. Though popular, "
|
|||
|
"the technique is somewhat tricky to get right and is best reserved for rare "
|
|||
|
"cases where there are large numbers of instances in a memory-critical "
|
|||
|
"application."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:886
|
|||
|
msgid "sequence"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:888
|
|||
|
msgid ""
|
|||
|
"An :term:`iterable` which supports efficient element access using integer "
|
|||
|
"indices via the :meth:`__getitem__` special method and defines a :meth:"
|
|||
|
"`__len__` method that returns the length of the sequence. Some built-in "
|
|||
|
"sequence types are :class:`list`, :class:`str`, :class:`tuple`, and :class:"
|
|||
|
"`bytes`. Note that :class:`dict` also supports :meth:`__getitem__` and :meth:"
|
|||
|
"`__len__`, but is considered a mapping rather than a sequence because the "
|
|||
|
"lookups use arbitrary :term:`immutable` keys rather than integers."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:897
|
|||
|
msgid ""
|
|||
|
"The :class:`collections.abc.Sequence` abstract base class defines a much "
|
|||
|
"richer interface that goes beyond just :meth:`__getitem__` and :meth:"
|
|||
|
"`__len__`, adding :meth:`count`, :meth:`index`, :meth:`__contains__`, and :"
|
|||
|
"meth:`__reversed__`. Types that implement this expanded interface can be "
|
|||
|
"registered explicitly using :func:`~abc.register`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:904
|
|||
|
msgid "single dispatch"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:906
|
|||
|
msgid ""
|
|||
|
"A form of :term:`generic function` dispatch where the implementation is "
|
|||
|
"chosen based on the type of a single argument."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:908
|
|||
|
msgid "slice"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:910
|
|||
|
msgid ""
|
|||
|
"An object usually containing a portion of a :term:`sequence`. A slice is "
|
|||
|
"created using the subscript notation, ``[]`` with colons between numbers "
|
|||
|
"when several are given, such as in ``variable_name[1:3:5]``. The bracket "
|
|||
|
"(subscript) notation uses :class:`slice` objects internally."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:914
|
|||
|
msgid "special method"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:916
|
|||
|
msgid ""
|
|||
|
"A method that is called implicitly by Python to execute a certain operation "
|
|||
|
"on a type, such as addition. Such methods have names starting and ending "
|
|||
|
"with double underscores. Special methods are documented in :ref:"
|
|||
|
"`specialnames`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:920
|
|||
|
msgid "statement"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:922
|
|||
|
msgid ""
|
|||
|
"A statement is part of a suite (a \"block\" of code). A statement is either "
|
|||
|
"an :term:`expression` or one of several constructs with a keyword, such as :"
|
|||
|
"keyword:`if`, :keyword:`while` or :keyword:`for`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:925
|
|||
|
msgid "struct sequence"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:927
|
|||
|
msgid ""
|
|||
|
"A tuple with named elements. Struct sequences expose an interface similar "
|
|||
|
"to :term:`named tuple` in that elements can either be accessed either by "
|
|||
|
"index or as an attribute. However, they do not have any of the named tuple "
|
|||
|
"methods like :meth:`~collections.somenamedtuple._make` or :meth:"
|
|||
|
"`~collections.somenamedtuple._asdict`. Examples of struct sequences include :"
|
|||
|
"data:`sys.float_info` and the return value of :func:`os.stat`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:933
|
|||
|
msgid "text encoding"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:935
|
|||
|
msgid "A codec which encodes Unicode strings to bytes."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:936
|
|||
|
msgid "text file"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:938
|
|||
|
msgid ""
|
|||
|
"A :term:`file object` able to read and write :class:`str` objects. Often, a "
|
|||
|
"text file actually accesses a byte-oriented datastream and handles the :term:"
|
|||
|
"`text encoding` automatically."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:943
|
|||
|
msgid "A :term:`binary file` reads and write :class:`bytes` objects."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:944
|
|||
|
msgid "triple-quoted string"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:946
|
|||
|
msgid ""
|
|||
|
"A string which is bound by three instances of either a quotation mark (\") "
|
|||
|
"or an apostrophe ('). While they don't provide any functionality not "
|
|||
|
"available with single-quoted strings, they are useful for a number of "
|
|||
|
"reasons. They allow you to include unescaped single and double quotes "
|
|||
|
"within a string and they can span multiple lines without the use of the "
|
|||
|
"continuation character, making them especially useful when writing "
|
|||
|
"docstrings."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:953
|
|||
|
msgid "type"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:955
|
|||
|
msgid ""
|
|||
|
"The type of a Python object determines what kind of object it is; every "
|
|||
|
"object has a type. An object's type is accessible as its :attr:`~instance."
|
|||
|
"__class__` attribute or can be retrieved with ``type(obj)``."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:959
|
|||
|
msgid "universal newlines"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:961
|
|||
|
msgid ""
|
|||
|
"A manner of interpreting text streams in which all of the following are "
|
|||
|
"recognized as ending a line: the Unix end-of-line convention ``'\\n'``, the "
|
|||
|
"Windows convention ``'\\r\\n'``, and the old Macintosh convention "
|
|||
|
"``'\\r'``. See :pep:`278` and :pep:`3116`, as well as :func:`bytes."
|
|||
|
"splitlines` for an additional use."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:966
|
|||
|
msgid "variable annotation"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:968
|
|||
|
msgid ""
|
|||
|
"A type metadata value associated with a module global variable or a class "
|
|||
|
"attribute. Its syntax is explained in section :ref:`annassign`. Annotations "
|
|||
|
"are stored in the :attr:`__annotations__` special attribute of a class or "
|
|||
|
"module object and can be accessed using :func:`typing.get_type_hints`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:974
|
|||
|
msgid ""
|
|||
|
"Python itself does not assign any particular meaning to variable "
|
|||
|
"annotations. They are intended to be interpreted by third-party libraries or "
|
|||
|
"type checking tools. See :pep:`526`, :pep:`484` which describe some of their "
|
|||
|
"potential uses."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:978
|
|||
|
msgid "virtual environment"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:980
|
|||
|
msgid ""
|
|||
|
"A cooperatively isolated runtime environment that allows Python users and "
|
|||
|
"applications to install and upgrade Python distribution packages without "
|
|||
|
"interfering with the behaviour of other Python applications running on the "
|
|||
|
"same system."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:985
|
|||
|
msgid "See also :mod:`venv`."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:986
|
|||
|
msgid "virtual machine"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:988
|
|||
|
msgid ""
|
|||
|
"A computer defined entirely in software. Python's virtual machine executes "
|
|||
|
"the :term:`bytecode` emitted by the bytecode compiler."
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:990
|
|||
|
msgid "Zen of Python"
|
|||
|
msgstr ""
|
|||
|
|
|||
|
#: ../Doc/glossary.rst:992
|
|||
|
msgid ""
|
|||
|
"Listing of Python design principles and philosophies that are helpful in "
|
|||
|
"understanding and using the language. The listing can be found by typing "
|
|||
|
"\"``import this``\" at the interactive prompt."
|
|||
|
msgstr ""
|